Sorry to disturb again.

This issue is because default the s:hidden tag will use xhtml as theme, but
actually in the distribution, there is no template/xhtml/hidden.ftl. It
always get from template/simple/hidden.ftl. But the cache does not know it.
Then this template is recompiled again and again.

Will report it to JIRA.

A bad news for me, just know my target .net project response time is around
0.3 second. Any suggestion to improve the speed? If I use apache work with
tomcat or any web server, can I get faster speed?

Regards,

Zheng Shuai

On 2/27/07, Shuai Zheng <[EMAIL PROTECTED]> wrote:

One more thing, this only happens on template/xhtml/hidden.ftl.

Should I report this as a bug?

On 2/27/07, Shuai Zheng < [EMAIL PROTECTED]> wrote:
>
> Dear All,
>
> Still do research on the debug log and try to get performance
> improvement, because I try to beat another .net system on speed(it can shows
> all the pages in 0.5 second,sigh).
>
> One more thing I just find out, if the log does not cheat me:)
>
> Although I have enabled the property template_update_delay=60000 in
> freemarker.properties and also move the template out the jar file.
> So there are a lot of log like:
> "[freemarker.cache]http-8080-Processor24
> template/xhtml/select.ftl[en_GB,UTF-8,parsed] cached copy not yet stale;
> using cached."
> So it looks correct. But also, there are something like followings:
>
> "Could not find template in cache, creating new one;
> id=[template/xhtml/hidden.ftl[en_GB,UTF-8,parsed]"
> "template/simple/hidden.ftl[en_GB,UTF-8,parsed] cached copy not yet
> stale; using cached."
> Above logs occur in the log again and again. I don't know what happened
> actually but it shows the hidden.ftl is not cached at all (how can this
> happens? when some others are cached?)
>
> Regards,
>
> Zheng Shuai
>
>
> On 2/26/07, Vlad2006 < [EMAIL PROTECTED]> wrote:
> >
> >
> > Hi Zheng,
> >
> > Have you profiled your application? Are you sure it is OGNL that makes
> > your
> > application slow?
> >
> > From my experience it is not so slow. At least I have not found it too
> > be a
> > bottleneck in my application. Not yet :-).
> >
> > What is really slow in WebWork/Struts2 is jsp tags like, textfield,
> > radio,
> > anchor, and other which are using FreeMarker templates.
> >
> > If it is your case, you could make it faster, you have to extract
> > templates
> > out of webwork.jar (in your case probably struts.jar) and put them in,
> > for
> > example, WEB-INF/templates directory.
> > There is a page on WebWork Wiki about it:
> > http://wiki.opensymphony.com/display/WW/Performance+Tuning
> >
> > I am not using Struts2 yet, but I believe most of the tips will work
> > for
> > Struts2.
> >
> > One more thing that could make application slower is when resource
> > bundles
> > are constantly reloaded. It is good for dev but not acceptable for
> > production. Check in struts property like: webwork.i18n.reload=false
> >
> >
> > Best regards
> > Vlad
> >
> >
> >
> > Shuai Zheng wrote:
> > >
> > > Dear All,
> > >
> > > I am using struts 2.0.6, but honestly the performance is very bad
> > (not
> > > need
> > > to think about scalability), to speed to load a simple page is much
> > slower
> > > than pure JSP (I haven't compared with struts 1). To refresh one
> > page it
> > > is
> > > 3-5 seconds with only one user. The profiler tells me the OGNL is
> > the
> > > bottleneck.
> > >
> > > I notice that there are some complains on OGNL about the performance
> > > already, may I know any other way to replace OGNL with anything else
> > to
> > > get
> > > a faster speed? Currently the speed is not acceptable for
> > production.
> > >
> > > Regards,
> > >
> > > Zheng Shuai
> > >
> > >
> >
> > --
> > View this message in context:
> > 
http://www.nabble.com/The-performance-issue-about-OGNL-tf3291137.html#a9157447
> > Sent from the Struts - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

Reply via email to