Return-Path: Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: (qmail 15725 invoked from network); 17 Sep 2010 16:47:08 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Sep 2010 16:47:08 -0000 Received: (qmail 35586 invoked by uid 500); 17 Sep 2010 16:47:08 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 35481 invoked by uid 500); 17 Sep 2010 16:47:07 -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 35473 invoked by uid 99); 17 Sep 2010 16:47:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Sep 2010 16:47:07 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pranavadesai@gmail.com designates 74.125.82.48 as permitted sender) Received: from [74.125.82.48] (HELO mail-ww0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Sep 2010 16:47:01 +0000 Received: by wwd20 with SMTP id 20so12491wwd.5 for ; Fri, 17 Sep 2010 09:46:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=bCn2x7dtdjG9j/vbqFjl6QloWbiR1bG2AngM9Ae8x+M=; b=oerJfRpy7T7/titSbb+dAB+BgdGX8P2sHqnPeG+jy/p7S4AE8b2ZzvfskRqLSKetSJ SV/RsOKEY/g8ztf1nweMSlf4eVA0FVxFidZBYgWYnV4+KyNtVO9UACxYsulQFMszrOKa JSi4Pw+xpGNe8ZksgafvRx0LVEOOvHv21jzC4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=vAIYddLtnPSku4eAc4rY2wBAKg+3rbclJufzbhWqdgKyhZRynlUE0DQJXUmgGVKFRc Jz85UcVTRNUKLSDILNJeEjuZHTA7soWVMNTvc+JoDM+3PXzlKs/gnUfQ55tZtS1SHxjo 8pgCZQp98feKWnTNGzfn70EAWW3JesFrmGDVY= MIME-Version: 1.0 Received: by 10.227.137.193 with SMTP id x1mr4438847wbt.80.1284741666065; Fri, 17 Sep 2010 09:41:06 -0700 (PDT) Received: by 10.227.131.3 with HTTP; Fri, 17 Sep 2010 09:41:06 -0700 (PDT) In-Reply-To: <4C937CB7.6070906@apache.org> References: <4C92C6B5.1070909@apache.org> <4C92D935.3000406@apache.org> <4C937CB7.6070906@apache.org> Date: Fri, 17 Sep 2010 09:41:06 -0700 Message-ID: Subject: Re: Need some help tuning for large file performance From: Pranav Desai To: users@trafficserver.apache.org, jplevyak@apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Sep 17, 2010 at 7:35 AM, John Plevyak wrote: > I just added a new option (and default) for large files to > the SVN repository. =A0 This dramatically improves performance > of large files, particularly on configurations with fewer > disks. What is the option ? > > I have tried to repro the crash issue with large files and > large ram disk to no avail. > > If you could try out the SVN version and make available > your testing procedure so that I can reproduce the issue > it would really help to get a fix. > I will try with the 2.1.2 version again to recheck if I screwed up something and see if I can reproduce it with the SVN version. I will create and update a thread for this issue on the dev list. -- Pranav > john > > On 9/16/2010 7:57 PM, Leif Hedstrom wrote: >> =A0On 09/16/2010 08:09 PM, Pranav Desai wrote: >>> On >>> Done. Using 2 disks. Do you recommend a raid config for better >>> performance ? >> >> No, I recommend RAID only if you really, really care for redundancy / >> reliability. ATS will automatically "load balance" across any disks that >> you throw at it. >> >>> >>> Here are my tcp mem parameters. And req/sec isnt of concern here so I >>> should be ok with the listen queue and backlogs. If you have any >>> particular setting in mind please let me know. >>> >>> net.ipv4.tcp_mem =3D 1339776 =A0 =A0 =A01786368 2679552 >>> net.ipv4.tcp_wmem =3D 4096 =A0 =A0 =A0 =A087380 =A0 8388608 >>> net.ipv4.tcp_rmem =3D 4096 =A0 =A0 =A0 =A087380 =A0 8388608 >> >> These would only make a difference if there's a latency between the >> client and the server (which is generally not the case in a "lab"). =A0T= he >> above are for the autoscaling window sizes I think, which seem >> reasonable. There are settings in records.config to bump up the initial >> window size for the connections: >> >> CONFIG proxy.config.net.sock_send_buffer_size_in INT 262144 >> CONFIG proxy.config.net.sock_recv_buffer_size_in INT 0 >> CONFIG proxy.config.net.sock_send_buffer_size_out INT 0 >> CONFIG proxy.config.net.sock_recv_buffer_size_out INT 0 >> >> >> You definitely want to tune that mmap setting I mentioned earlier, and a >> few other interesting sysctl's would be >> >> =A0 =A0 net.ipv4.tcp_max_syn_backlog (set it pretty high) >> =A0 =A0 net.core.somaxconn >> =A0 =A0 net.ipv4.tcp_syncookies (enable it) >> =A0 =A0 net.ipv4.ip_local_port_range >> =A0 =A0 net.ipv4.tcp_ecn (probably want it disabled) >> =A0 =A0 net.ipv4.tcp_max_tw_buckets (increase for lots of sockets I thin= k) >> >> >>> >>> I think I can reproduce it but under load, so it might be a bit >>> difficult to debug it especially with all the threads. I will try to >>> get to a simpler test case to reproduce it. Maybe I can run >>> traffic_server alone with a single network and io thread ? How do you >>> guys normally debug it ? >> >> >> I think we should move the discussions related to this crasher problem >> to the dev@trafficserver.apache.org mailing list (information how to >> subscribe to it is on http://trafficserver.apache.org). There's a wider >> crowd there that might be able to help as well, in particular John >> Plevyak knows the cache better than anyone else on the planet. >> >> That much said, if you can reproduce it with restrictions like you >> mention, that'll certainly help. Or, just describe how to setup the >> environment, and what "load" to send to it, that might also help. But >> the more you can limit the parameters / tests / time necessary to >> reproduce it, the better. >> >> Thanks! >> >> -- leif > >