Return-Path: Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: (qmail 31799 invoked from network); 1 Jan 2011 19:00:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jan 2011 19:00:52 -0000 Received: (qmail 43927 invoked by uid 500); 31 Dec 2010 18:00:50 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 43908 invoked by uid 500); 31 Dec 2010 18:00:49 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 43898 invoked by uid 99); 31 Dec 2010 18:00:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Dec 2010 18:00:49 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [76.96.27.227] (HELO qmta12.emeryville.ca.mail.comcast.net) (76.96.27.227) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Dec 2010 18:00:39 +0000 Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta12.emeryville.ca.mail.comcast.net with comcast id ptDh1f0030S2fkCACu0KYN; Fri, 31 Dec 2010 18:00:19 +0000 Received: from [192.168.1.3] ([24.7.89.76]) by omta09.emeryville.ca.mail.comcast.net with comcast id pu0D1f0081eq6NG8Vu0EkP; Fri, 31 Dec 2010 18:00:16 +0000 Message-ID: <4D1E19AA.3050103@apache.org> Date: Fri, 31 Dec 2010 09:58:02 -0800 From: John Plevyak Reply-To: jplevyak@apache.org Organization: The Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: users@trafficserver.apache.org Subject: Re: Questions before researching a move from squid References: <02FE106AE6B85F4289AACCDC67F130C81750A9048F@EXCHMAIL.staff.internode.com.au> In-Reply-To: <02FE106AE6B85F4289AACCDC67F130C81750A9048F@EXCHMAIL.staff.internode.com.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I can answer 2 of these. On 12/29/2010 5:16 PM, Kingsley Foreman wrote: > > Hi Guys, > > > > I've been using squid in a reverse proxy environment for some time now, and am pretty unimpressed with its performance and lack of scalability and im looking at giving Traffic Server a bit of a trial. But before I do that I need to know if it supports a couple of things because if it doesn't then there is no point me testing. And yes some of these things are annoying and silly but out of my control. > > > > 1. Large files i need the ability to cache files 8gb and up (it is for a remote edge server and these happen every now and then). > > ATS 2.1+ can cache files up to the size of a partition (a disk/raid device) up to .5PB (500TB). > > 2. range_offset_limit like setting, There is a client, that does 206 queries starting at byte range 0 (and of course others), i need them to still cache. You can cache range requests by setting: proxy.cache.http.cache.range.lookup to 1. Range requests are cached separately from whole documents currently, so the range request must match to be found in the cache. > > > > 3. ICP based on lowest latency > > > > 4. nice but not required would also be esi > > > > I guess the question is is Traffic Server for me, and should I give it a decent trial? > > > > Kingsley