Hi Adrian,
Happy to see your input :)
[Adrian Chadd:]
| > | I'm surprised some of these (like logging) must be chosen at
| > | compile-time, that's quite limiting.
| >
| > If the logging is disabled during compile time, It is removed completely
| > from the Request Path. (Introducing no overhead at all). While even if
| > the logging is enabled during compile time, The administrator can
| > disable it from the squid.conf file. (With a --possibly small -- overhead
| > for checking the squid.conf option)
|
| Logging itself isn't high overhead. The fact squid-2.6 and Squid-3 right now
| log using stdio in the same single-threaded process is the problem if
| administrators -wanted- to keep logs.
in this case, if we enable the all logs during compile time, And the
Squid administrator disables them in squid.conf, would there be a
significant difference between this, and the case where the options are
disabled during compile time itself?
| I've written some proof of concept code (s26_logfile_daemon branch at
| squid.sf.net) which breaks out logfile writing to an external process.
I will check this out.
| If you want to know where the CPU is hiding then grab a copy of polygraph
| (http://www.web-polygraph.org/), configure a client/server, setup a Squid
| proxy server, run the Polymix-4 test suite and do some Squid profiling.
| My s26_logfile_daemon branch removes stdio logfile writes as a bottleneck
| (around a couple hundred requests a second with stdio; up to a few
| thousand a second..) but the Squid bottlenecks are elsewhere.. :)
|
| (don't forget to compile squid-2.6 with --enable-dev-poll either.)
thanks, I will add this too.
rahul
--
1. e4 _
