Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4CBE710A64 for ; Fri, 14 Nov 2014 03:16:03 +0000 (UTC) Received: (qmail 12798 invoked by uid 500); 14 Nov 2014 03:15:58 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 12739 invoked by uid 500); 14 Nov 2014 03:15:57 -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 12729 invoked by uid 99); 14 Nov 2014 03:15:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Nov 2014 03:15:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ming.zym@gmail.com designates 209.85.192.181 as permitted sender) Received: from [209.85.192.181] (HELO mail-pd0-f181.google.com) (209.85.192.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Nov 2014 03:15:29 +0000 Received: by mail-pd0-f181.google.com with SMTP id y10so15648093pdj.26 for ; Thu, 13 Nov 2014 19:15:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=4JpMmZgLopYsnTRslv2izYb0ZEzzlO/U8Sora4+noIc=; b=wMag0Qg3iwjMO3GoqeW3L3MYnzeznh39ve+IetP6PNXz9DU92KsanvtX3rorHTNewQ lAeAaRBpDK3/NMKYlDUjMYBnA51DXlMA4WwwStsvGfWCvU5eHVOQ164ufAnRffAiS9LD SsIu48LfntelDzA9WcX4bkecrY6wNYKxy82E6zwGqvV08y0pF3NHQc8mf5WNniZVKk6D CWooslYtmGfxs2TJ9glF66PgG+0xw3dz/mSWGr/mCQ9BDg9ZVL4Ai/eL2ed/CxowzFDL uY8QBU5QgEnEvWheD8bP8rgvSNQtVYVbLztAmQ2BAgXLZsO20PVz3AXEKl23jzIFK1GI 8Tdw== X-Received: by 10.70.45.233 with SMTP id q9mr7321836pdm.24.1415934927861; Thu, 13 Nov 2014 19:15:27 -0800 (PST) Received: from [192.168.1.4] ([111.193.190.166]) by mx.google.com with ESMTPSA id p10sm23381284pds.63.2014.11.13.19.15.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Nov 2014 19:15:26 -0800 (PST) From: Yongming Zhao Content-Type: multipart/alternative; boundary="Apple-Mail=_8BBAA548-FC18-4827-8D55-B38B2464C7A3" Message-Id: <70099DBF-EC1F-4459-9F42-4252C6966579@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: proxy.config.cache.ram_cache.size query from eBay Date: Fri, 14 Nov 2014 11:15:20 +0800 References: <6C3FE60A54A2274F8668094C2D9556B66E821648@PHX-EXRDA-S92.corp.ebay.com> To: users@trafficserver.apache.org In-Reply-To: <6C3FE60A54A2274F8668094C2D9556B66E821648@PHX-EXRDA-S92.corp.ebay.com> X-Mailer: Apple Mail (2.1990.1) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_8BBAA548-FC18-4827-8D55-B38B2464C7A3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=gb2312 please provide more information: 1, ATS version 2, object size setting: traffic_line -r proxy.config.cache.min_average_object_size 3, mem dump info: follow = https://docs.trafficserver.apache.org/en/latest/sdk/troubleshooting-tips/d= ebugging-memory-leaks.en.html = and attach the result from traffic.out. - Yongming Zhao =D5=D4=D3=C0=C3=F7 > =D4=DA 2014=C4=EA11=D4=C214=C8=D5=A3=AC=C9=CF=CE=E710:40=A3=ACLerner, = Steve =D0=B4=B5=C0=A3=BA >=20 > Hi gang- Phil Sorber referred me to this list. > =20 > We are setting up clusters of Apache Traffic Server to beef up the = front end of our image services which are=A1=AD large in terms of = volume=A1=AD to say the least. > We hope to be the big users of ATS and be a strong reference customer- = so any help with is appreciated! > Our first test cluster consistes of 23 machines, ubuntu12.04, Intel(R) = 2x Xeon(R) CPU E5-2670 v2 @ 2.50GHz, 128G ram, 95T disk > =20 > Here is our query: > =20 > We are setting records.config as: CONFIG = proxy.config.cache.ram_cache.size INT 64G > =20 > But we find that trafficserver ignores this limit and grows at the = default rate of 1MB RAM / 1GB disk. > =20 > Example of a current process:=20 > =20 > traffic_line -r proxy.config.cache.ram_cache.size returns = 68,719,476,736 > Which is about 64GB- correct! >=20 > But looking at the process: > =20 > 86050 nobody 20 0 108g 102g 4912 S 54 81.3 1523:33 = /ebay/local/trafficserver/bin/traffic_server -M --httpport 80:fd=3D7 > =20 > So basically we=A1=AFve set the process to only consume 64GB but its = consuming 108GB=A1=AD >=20 > Does anyone have any ideas on why this happens or a way to fix it? > We want to have constrained RAM but tons of disk- we=A1=AFd much = rather have the cache serve from disk then start swapping RAM > =20 > Thanks in advance, > =20 > Steve > =20 > Steve Lerner | Sr. Member of Technical Staff, Network Engineering | M = 212 495 9212 | slerner@ebay.com | Skype: = steve.lerner > --Apple-Mail=_8BBAA548-FC18-4827-8D55-B38B2464C7A3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=gb2312
please provide more information:
1, ATS version

2, object size setting:
traffic_line = -r proxy.config.cache.min_average_object_size

3, mem dump = info:
follow https://docs.trafficserver.apache.org/en/latest/sdk/troubleshoo= ting-tips/debugging-memory-leaks.en.html and attach the result = from traffic.out.



- Yongming Zhao = =D5=D4=D3=C0=C3=F7

=D4=DA 2014=C4=EA11=D4=C214=C8=D5=A3=AC=C9=CF=CE=E710:40=A3=ACL= erner, Steve <slerner@ebay.com> =D0=B4=B5=C0=A3=BA

Hi gang- = Phil Sorber referred me to this list.
 
We are setting up clusters of Apache = Traffic Server to beef up the front end of our image services which = are=A1=AD large in terms of volume=A1=AD to say the least.
We hope = to be the big users of ATS and be a strong reference customer- so any = help with is appreciated!
Our first test cluster consistes of 23 machines, ubuntu12.04, = Intel(R) 2x Xeon(R) CPU E5-2670 v2 @ 2.50GHz, 128G ram, 95T disk
 
Here is = our query:
 
We are setting records.config as: CONFIG proxy.config.cache.ram_cache.size INT = 64G
 
But we find that trafficserver ignores this limit and grows = at the default rate of 1MB RAM / 1GB disk.
 
Example of a current process: 
 
traffic_line -r = proxy.config.cache.ram_cache.size returns 68,719,476,736
Which is about 64GB- correct!

But looking at the process:
 
86050 nobody    20   0  108g 102g 4912 S   54 = 81.3   1523:33 /ebay/local/trafficserver/bin/traffic_server -M = --httpport 80:fd=3D7
 
So basically we=A1=AFve set the process = to only consume 64GB but its consuming 108GB=A1=AD

Does anyone have any ideas on why this happens or a way to = fix it?
We want to have constrained RAM but tons of disk- we=A1=AFd = much rather have the cache serve from disk then start swapping RAM
 
Thanks in = advance,
 
Steve
 
Steve = Lerner | Sr. Member of Technical = Staff, Network Engineering | M 212 495 9212 | slerner@ebay.com | Skype: steve.lerner
<image001.jpg>

= --Apple-Mail=_8BBAA548-FC18-4827-8D55-B38B2464C7A3--