Massimiliano, your actual script execution time is 0.1485 seconds. Counting the time it takes to empty the output buffer for transfering the contnet to the client you have 0.23 seconds.
It looks like the time is spent on rendering the debug output. Do you use debug output in a popup window? Can you try to disable the debug output and benchmark the page?
@Baard: I usually debug inline and those are the results from the inline version. I tried to switch to popup, just to check, and it takes even longer, plus I get a kernel 20 error in the popup, saying "the module "var" which you requested was not found" instead of the debug output. Trying to turn completely off debug strangely makes the public page load take a whopping 39 seconds to generate (taken by hand, I'll restart firefox now and use a specific tool for better checking, then I'll add more precise figures).
Ok here are the more accurate figures, taken with LORI FF extension. values are : click-to-first-byte sent back, and click-to-end-of-page-sending
home page public siteaccess: 10.344, 31.15 seconds
home page public siteaccess reload: 10.344, 31.16 seconds
home page public siteaccess reload: 10.328, 30.969 seconds
home page admin siteaccess: 10.313, 10.500 seconds,
21 seconds from successful login to content tree display 20.780, 20.781 secs
11 seconds from there to settings tab 10.750, 11.93 secs 11 seconds from settings tab to again content tree view 10.687, 11.218 seconds
great, that made my day, now page serving time is back to normality. Now I guess my sysadmin will need to investigate why on this peculiar machine I need to keep persistent connections on for it to work well. I have done my part ;-)
Great ;) You are welcome Max! Share your information with other eZ users, if you will find someone with similar problem don't hesitate to post an answer ;)