This is a discussion on Re: [squid-users] Evaluating SQUID as a Reverse Proxy for a large web site - squid ; Henrik, I am using Apache as my web server. I decreased the dish cache size to 1 MB and re-ran my tests. This time i got all TCP_MEM_HITS for the images and static files. However my benchmark results were not ...
I am using Apache as my web server. I decreased the dish cache size to 1 MB
and re-ran my tests. This time i got all TCP_MEM_HITS for the images and
static files. However my benchmark results were not better. The web server
still scaled much better.
My guess is that SQUID cannot handle concurrency too well. How do i get
SQUID to increase the no of processes or threads? Is my only option to have
many SQUID servers on different ports on a host with lot of RAM, running in
front of a load balancer to handle concurrency?
----- Original Message -----
From: "Henrik Nordstrom"
To: "kapil khanna"
Sent: Sunday, March 07, 2004 3:28 AM
Subject: Re: [squid-users] Evaluating SQUID as a Reverse Proxy for a large
> On Sat, 6 Mar 2004, kapil khanna wrote:
> > I have been evaluating SQUID to deploy in front of a large web site to
> > all static content (Images, JS Files, CSS Files, HTML files etc...) for
> > web site. I used JMeter as a load testing tool to evaluate the
> > of SQUID. This is my current config:-
> > cache_mem - 256MB
> > disk cache - 10MB.
> > I purposely have a very low disk cache so that i can get most out of
> > in-memory caching of static content. I also set content expiry (if not
> > for images, JSP files etc to
> > 14400 80% 43200
> You probably should run without any disk cache at all in this
> configuration. If not Squid will not actually be able to use all that
> > Why is that the Web application scales better than SQUID? The one thing
> > that stands out is that SQUID is running as one process one thread,
> > whereas the web site is multithreaded.
> What kind of web server are you using?
> The benefits of using a cache infront of the web server is mostly seen if
> the web server can not handle very many concurrent connections. The cache
> then helps both by offloading the static content any by reusing the same
> persistent connections for multiple clients.