Lo All -
I have an installation of RedHat 7.0 stripped down, secured, and patched
up (all the appropriate rpm updates and a 2.4.1 kernel update) running
the current version of Squid (Version 2.3.STABLE4). I have adjusted the
file descriptors, configured for local DNS lookups, and adjusted every
parameter suggested in the FAQ. The machine is an 950 MHz Athlon with
768MB of RAM, and the cache dirs are on 4 18GB Ultra 160 SCSI disks. I
can send along more in depth specs as necessary.
The traffic consists of approximately 300 dial-ups, a few DSL lines, and
some office traffic. The redirection of web requests is handled by a
Foundry Layer 4 switch, and the recommended ipchains commands.
Yet, under the afternoon, and evening load, the Squid installation slows
down significantly. So, The following questions are my next step in
resolving this performance issue.
Please, assume I have read the FAQ. Some of the following questions can
and have been answered by the FAQ. However, I am hoping for a more
concise, and possibly more current digest of the facts as they relate.
:-)
TIA!
1. What is considered a heavy workload for a Squid server? What can it
handle?
2. What version (patches, etc . . .) of Squid is recommended for a Squid
server under heavy workload?
3. What are the recommended adjustments to Squid for heavy workloads?
4. What are the recommended adjustments to the Linux OS to ensure proper
operation?
5. Is there one OS which runs Squid better than all others?
6. What is the most effective redirector for the local machine to pick
up transparent caching requests forwarded from a layer 4 switch?
Bryan Campbell
bbc@misn.com
-- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Sun Mar 04 2001 - 20:06:29 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:58:31 MST