Simply by adding WebMacroSiteNavigation based classes for the
navigations
I'm down to 500ms. For some reason I go from 2400ms to 500ms just for
adding classes for my navigations..
Does it seems reasonable that 300ms of the 500 should be happening after
doBuildTemplate for the screen is done? In otherwords most of the
processing
time is in TurbineWebMacroService.handleRequest?
If I'm at the best I can do I'm okay for now, but I wouldn't think that
processing templates (when webmacro is caching) would be the most
significant part of the pageload.
Throughout testing this I haven't changed my doBuildTemplate for the
screen and that part of the pagebuild is less than 40% of the time.
Should I be looking elsewhere for speed?
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
