Kirk, Well - yes and no. JIRA uses OSCache, but not for the UI tags. None of those are cached at all, and we have literally hundreds ;)
OSCache is only used where certain pages take a long time to generate for various reasons (most often because of the computations required to calculate the data set being displayed). We also use a lot of select tags, some with up to 100 elements, and their time to render is not significant? Cheers, Mike On 15/1/03 12:34 PM, "Kirk Rasmussen" ([EMAIL PROTECTED]) penned the words: > I assume that JIRA uses OSCache, right? Jive 3.0 default skin > uses webwork also but they avoid the UI tags completely. > > Here is what I did to make my countries list very fast. > > It isn't ideal but it works and it was plugin compatible to the > <ui:select> tag. > > FYI I got the execution time down from 13 seconds to 0.0020 seconds. > > >> -----Original Message----- >> From: Peter Kelley [mailto:[EMAIL PROTECTED]] >> Sent: Tuesday, January 14, 2003 4:23 PM >> To: [EMAIL PROTECTED] >> Subject: Re: [OS-webwork] Scope for 1.4 >> >> >> Mike, >> >> We use JIRA and the performance is fine but our product webwork code >> performance is awful at the moment. Have you any tips for the >> performance challenged ? >> >> >> >> On Tue, 2003-01-14 at 16:00, Mike Cannon-Brookes wrote: >>> Kirk, >>> >>> As a guide, we've been shipping code based on 1.3 for a few >> months now. And >>> yes, we use millions of UI tags ;) >>> >>> I agree with you in general though - talk of 1.4 is silly >> when 1.3 isn't out >>> yet! >>> >>> Cheers, >>> Mike >>> >>> ATLASSIAN - http://www.atlassian.com >>> Expert J2EE Software, Services and Support >>> >>> On 14/1/03 7:34 AM, "Kirk Rasmussen" >> ([EMAIL PROTECTED]) penned >>> the words: >>> >>>> Hello everyone! >>>> >>>> I'm very pleased to make the transition towards using the WW >>>> framework for our development group and I would like to >>>> contribute back to the project. >>>> >>>> I choose to use WW over Struts as our standard MVC framework >>>> about a month ago after reading about it in various blogs and >>>> mailing lists. I downloaded the 1.2.1 version and started >>>> developing with it because it was the only release available at >>>> the time. >>>> >>>> After using WW for about 3 weeks and as an outside observer on >>>> this list for some time now it seems to me that there needs to be >>>> separate teams focused on the 1.2, 1.3, XWork, and now 1.4 >>>> branches?? >>>> >>>> There are a number of issues that still need to be resolved with >>>> the 1.2 release IMHO. I've spoken with a number of people with >>>> more WW experience than I and the common theme I've heard is >>>> "don't use the UI tags". >>>> >>>> Why is that? Now that I've used them I know why...performance. >>>> As a new user it is disconcerting that the WW docs and examples >>>> are geared towards using the UI tags but in real world usage now >>>> I've been told not to use them by a number of people. I >> have gotten >>>> a lot of helpful advice on how to solve the performance problem >>>> (e.g. OSCache, patching BeanUtil class, etc.) but if WW is to grow >>>> as a community like Struts has, I think the current >> branch needs to >>>> be polished before moving on to the next big thing (1.3, XWork >>>> or 1.4?) >>>> >>>> I realize that the UI tags aren't necessary and that they are only >>>> a small part of the rest of the WW architecture. In our >> environment, >>>> the engineers are out numbered by the content folks by an >> 5 to 1 ratio. >>>> It is important that the pages be as simple as possible. >> Our pages that >>>> are released to production tend to get duplicated (copy & >> paste from >>>> examples) and maintenance of the pages becomes a nightmare. >>>> >>>> I think new users will tend to download the most stable >> version of a product >>>> instead of the latest cutting edge version especially >> when documentation is >>>> lacking. >>>> >>>> What do you guys think? Is 1.2 a lost cause at this >> point? Is it better >>>> to focus on the 1.3 release only? >>>> >>>> Regards, >>>> Kirk Rasmussen >>>> Lucasfilm Ltd. >>>> >>>>> -----Original Message----- >>>>> From: Jason Carreira [mailto:[EMAIL PROTECTED]] >>>>> Sent: Monday, January 13, 2003 11:17 AM >>>>> To: [EMAIL PROTECTED] >>>>> Subject: [OS-webwork] Scope for 1.4 >>>>> >>>>> >>>>> So, after we finally push 1.3 out the door, we're going to >>>>> need an idea >>>>> of what should be in 1.4. My suggestion would be refactor the >>>>> GenericDispatcher and ActionFactory to put the Interceptor >>>>> code in, and >>>>> have a relatively quick release after 1.3 with that stuff >>>>> added (and any >>>>> bug fixes). >>>>> >>>>> Thoughts? >>>>> >>>>> Jason >>>>> >>>>> -- >>>>> Jason Carreira >>>>> Technical Architect, Notiva Corp. >>>>> phone: 585.240.2793 >>>>> fax: 585.272.8118 >>>>> email: [EMAIL PROTECTED] >>>>> --- >>>>> Notiva - optimizing trade relationships (tm) >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> This SF.NET email is sponsored by: FREE SSL Guide from Thawte >>>>> are you planning your Web Server Security? Click here to >> get a FREE >>>>> Thawte SSL guide and find the answers to all your SSL >>>>> security issues. >>>>> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en >>>>> _______________________________________________ >>>>> Opensymphony-webwork mailing list >>>>> [EMAIL PROTECTED] >>>>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >>>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.NET email is sponsored by: FREE SSL Guide from Thawte >>>> are you planning your Web Server Security? Click here to >> get a FREE >>>> Thawte SSL guide and find the answers to all your SSL >> security issues. >>>> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en >>>> _______________________________________________ >>>> Opensymphony-webwork mailing list >>>> [EMAIL PROTECTED] >>>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.NET email is sponsored by: FREE SSL Guide from Thawte >>> are you planning your Web Server Security? Click here to get a FREE >>> Thawte SSL guide and find the answers to all your SSL >> security issues. >>> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en >>> _______________________________________________ >>> Opensymphony-webwork mailing list >>> [EMAIL PROTECTED] >>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >> -- >> Peter Kelley <[EMAIL PROTECTED]> >> Moveit Pty Ltd >> >> >> >> ------------------------------------------------------- >> This SF.NET email is sponsored by: Take your first step >> towards giving >> your online business a competitive advantage. Test-drive a Thawte SSL >> certificate - our easy online guide will show you how. Click >> here to get >> started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en >> _______________________________________________ >> Opensymphony-webwork mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >> > ------------------------------------------------------- This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
