Peter M. Jansson wrote:
> The big secret to tuning AOLserver is that there isn't much to tune.
> There's minimal gain to be made by increasing the transmission buffer
> sizes in nssock, and you can play with the MaxThreads, increasing it
> until contention begins to dominate your timing.
I've never tuned my AOLserver and it works fine for high load (we get
that from time to time).
> Most people I've encountered trying to tune AOLserver are saddled
> with slow applications which really don't respond to tuning.
For this I've written a small benchmarking module. I've rewritten the
adp parser to add something like '<% adpbenchmark begin %>' at the
beginning of the file, then registered a trace filter and used
Ns_GetTime+Ns_DiffTime to get the time difference.
In order not to overload the memory, I used Ns_CacheCreateSz() and used
it for storing data on files - it is 1MB size and each entry is 24 bytes
long.
This helps in checking which dynamic pages require a lot of time to
render them.
A bit offtopic, but how do I register any filter that is called *before*
a request is parsed and evaluated? I tried pre_auth and trace with <%
ns_sleep 2 %> but the time difference was not even near 1s :(
--
WK
"Data typing is an illusion. Everything is a sequence of bytes."
-Todd Coram
