Mike, I should qualify that I am running the 1.2.1 build for my tests. I have not tried 1.3 RC1 yet.
However, even when I eliminated the <ui:select> tag and used a straight <webwork:iterator> to product the select list it only reduced the execution time to 10 secs versus 13 secs. To me this poses a significant problem, at least for the 1.2 build. Has anyone profiled webwork with JProbe or similar tools to look for hot spots that could be optimized? > -----Original Message----- > From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 14, 2003 5:56 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Scope for 1.4 > > > 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 > ------------------------------------------------------- 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
