Hi,
As you experience Squid is not optimally tuned to be running as a web
server accelerator. A lot of small knobs is missing to tune it to
this kind of workload which is a bit different from that of a HTTP
Proxy for which Squid was/is designed.
It is not that these at large conflict with the design of Squid, only
that nobody has got to the point of doing them, and to do them in
such a manner that they do not conflict with the use of Squid as a
HTTP proxy (which may be a philosofical problem in some cases..).
Regards
Henrik
On Sunday 14 July 2002 23.22, Rolf Weber wrote:
> Hello everybody,
>
> I had to accelerate a high traffic webserver with lots of very very
> enormous PHP-scripts, I took squid in accelerator mode with
> suitable refresh_patterns, and it did a really good job - the load
> on the webserver decreased significantly.
>
> However - its job could be much better. :-)
> When requests arrive simultaneously and the corresponding cache
> entries are outdated, squid forwards these requests simultaneously
> to the webserver - and this behavior is still really bad for the
> webserver in peek times ...
>
> With my understanding, it would be much better, if squid would
> recognize it's already reloading the request from the webserver and
> answer all other requests with the "old" cache entries until it has
> the new ones.
>
> I couldn't find any information on this problem, only one post to
> this list
> (http://www.squid-cache.org/mail-archive/squid-users/200110/1089.ht
>ml) which unfortunatly stood unanswered ...
>
> I fear my wishes do conflict with the philosophy squid was written
> and there is no easy way to implement it - but before I have to
> start hacking I better ask first this list ... :-)
>
> rolf
Received on Sun Jul 14 2002 - 17:25:47 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:09:14 MST