I'd love to hear the thoughts on this as well. We (Flickr) run squid 2 with what might be a very specific use-case: constantly full and churning reverse-proxy caching, making use of both memory and disk. Until 3 has some of the things that Mark points out, and gains stability for our use, we won't be able to test it out. The roadmap that appears on the wiki for 2 appears to be more in-line than 3 with what we'll be looking for (and could probably get sponsorship for) from future squid versions. John Allspaw manager, operations engineering flickr.com ----- Original Message ---- > From: Tony Dodd <tony@xxxxxxx> > To: Mark Nottingham <mnot@xxxxxxxxxxxxx> > Cc: Squid Users <squid-users@xxxxxxxxxxxxxxx> > Sent: Wednesday, February 27, 2008 4:50:26 AM > Subject: Re: Squid-2, Squid-3, roadmap > > Mark, thanks for raising these questions, we at Last.FM are facing the > same issues as Yahoo! is wrt squid-2/-3. > > In answer to your final question in the list, I've tested -3 on a > number of servers over a number of time-periods during the past few > months. Unfortunately, the missing features found within -2, combined > with sluggish overall response times and higher server load make it > impossible for me to move over to it for our production squid cluster. > > -Tony > > -- > Tony Dodd, Systems Administrator > > Last.fm | http://www.last.fm > Karen House 1-11 Baches Street > London N1 6DL > > check out my music taste at: > http://www.last.fm/user/hawkeviper > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
