Eric E. Meyer wrote:
Bertrand Delacretaz wrote:
Le 17 mars 05, � 18:30, Eric E. Meyer a �crit :
...Some pages in the site scale quite well, while one in particular does not scale well at all..
Did you try to run tests on just that page, many same requests, and try removing components from the page generation path, one after the other?
This should help you isolate the component that causes the problem, to narrow your search.
You could also create a request-specific logger, one for each request, store it in the request context and use it to log times at various stages, with a unique request ID. This would help find worst case times.
-Bertrand
These are great ideas. Any other suggestions as to how to get a better picture of what's going on? It's been a bit frustrating trying to get a complete picture? For example, is there a way to see monitor the avalon component pool sizes and utilization?
Haha :-) calls for "instrumentation"
Cheers
Giacomo
PS: Eric, sorry, this is an insider joke you might not understand but I couldn't resist to do as 6 month ago the Instrumentation code was removed.
-- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
smime.p7s
Description: S/MIME Cryptographic Signature
