Sorry din sa off-topic na nai-post ko patunkol sa varnish... ----- Eto na ang topic:
Squid Squid has been around pretty much since the start of the Web, as an outgrowth of the Harvest project. While it's probably also the most widely deployed caching proxy, it's been criticised because it doesn't perform very well. In particular, when it's overloaded it behaves very badly, increasing the response times as load increases, eventually delaying for multiple seconds and dropping lots of connections. However, Squid 2.6 was recently released, with support for epoll and kqueue. My testing shows it as being much better-behaved under load; response times are perfectly flat at about 180ms during overload, no matter what the request rate. 2.6 was also able to hold 15,000 persistent connections open without any noticeable change in response rate or latency. Impressive. Squid 2.6 doesn't perform quite as well in terms of raw capacity (serving about 7,500 small responses per second, vs. 2.5's 9,000), but hopefully it'll get better as the 2.6 line matures. One thing that still concerns me about Squid is that its capacity drops much more than other proxies do when response sizes get larger. Overall, Squid is a good workhorse that's somewhat limited by its age; since it it's single-process and single-threaded, it can't take advantage of multiple cores, putting it at a severe disadvantage against threaded servers. Still, it's very configurable, has good instrumentation, and is a known quantity. Not a bad option. _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
