Return-Path: Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: (qmail 31719 invoked from network); 14 Jul 2010 16:12:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Jul 2010 16:12:27 -0000 Received: (qmail 9986 invoked by uid 500); 14 Jul 2010 16:12:27 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 9912 invoked by uid 500); 14 Jul 2010 16:12:26 -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 9904 invoked by uid 99); 14 Jul 2010 16:12:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 16:12:26 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [71.6.165.248] (HELO kramer.ogre.com) (71.6.165.248) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 16:12:16 +0000 Received: from loki.ogre.com (homey.ogre.com [24.56.189.145]) (authenticated bits=0) by kramer.ogre.com (8.14.3/8.14.3) with ESMTP id o6EGBqxP022150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Jul 2010 09:11:52 -0700 X-DKIM: Sendmail DKIM Filter v2.8.3 kramer.ogre.com o6EGBqxP022150 Message-ID: <4C3DE1C8.6080807@apache.org> Date: Wed, 14 Jul 2010 10:11:52 -0600 From: Leif Hedstrom User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100621 Fedora/3.0.5-1.fc13 Thunderbird/3.0.5 MIME-Version: 1.0 To: users@trafficserver.apache.org CC: Rob Maidment Subject: Re: why does cache hit rate tail off? References: <1C38D729-ED26-4A0F-B37D-674C0589CA69@apache.org> In-Reply-To: Content-Type: multipart/alternative; boundary="------------060503070601010304040607" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------060503070601010304040607 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 07/14/2010 10:02 AM, Rob Maidment wrote: > > The old (LRU) algorithm made little difference. > > I guess it could be that I’m simply exceeding the cache capacity. The > test uses a working set of 2.24GB. How do I configure the size of the > cache? > Two settings: In etc/trafficserver/storage.config, you will see a line similar to var/trafficserver 140M You'll want that closer to 2.24G I imagine :). For the RAM cache, the setting is in etc/trafficserver/records.config: CONFIG proxy.config.cache.ram_cache.size INT -1 The default (-1) means it'll calculate the RAM cache size based on the disk cache size; For every 1GB of disk cache, it uses 1MB of RAM cache (which is really small honestly). I'd definitely bump this up as much as your box can handle, but make sure to leave room for the connections and other buffers (setting this is a "trial and error", and is very application specific). Fwiw, an inactive connection consumes about 32KB of memory, and an active one doubles that (for additional buffers). SSL connections consumes even more memory. (I think this is an area where we might be able to improve too, patches are welcomed). I hope any of this helps your benchmarks (really looking forward to see your results). -- leif --------------060503070601010304040607 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 07/14/2010 10:02 AM, Rob Maidment wrote:

 

The old (LRU) algorithm made little difference.

I guess it could be that I’m simply exceeding the cache capacity.  The test uses a working set of 2.24GB.  How do I configure the size of the cache?


Two settings:

In etc/trafficserver/storage.config, you will see a line similar to

    var/trafficserver 140M


You'll want that closer to  2.24G I imagine :). For the RAM cache, the setting is in etc/trafficserver/records.config:

    CONFIG proxy.config.cache.ram_cache.size INT -1


The default (-1) means it'll calculate the RAM cache size based on the disk cache size; For every 1GB of disk cache, it uses 1MB of RAM cache (which is really small honestly). I'd definitely bump this up as much as your box can handle, but make sure to leave room for the connections and other buffers (setting this is a "trial and error", and is very application specific). Fwiw, an inactive connection consumes about 32KB of memory, and an active one doubles that (for additional buffers). SSL connections consumes even more memory. (I think this is an area where we might be able to improve too, patches are welcomed).

I hope any of this helps your benchmarks (really looking forward to see your results).

-- leif

--------------060503070601010304040607--