From users-return-6957-archive-asf-public=cust-asf.ponee.io@trafficserver.apache.org Fri Feb 16 22:34:17 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 74413180647 for ; Fri, 16 Feb 2018 22:34:16 +0100 (CET) Received: (qmail 52442 invoked by uid 500); 16 Feb 2018 21:34:15 -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 52433 invoked by uid 99); 16 Feb 2018 21:34:15 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2018 21:34:15 +0000 Received: from rav1-1-gci-pool-general-10-87-130-163.corp.yahoo.com (nat-dip15.fw.corp.yahoo.com [209.131.62.124]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 7F9985C9 for ; Fri, 16 Feb 2018 21:34:12 +0000 (UTC) From: Bryan Call Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Understanding RAM cache size and limits Date: Fri, 16 Feb 2018 13:34:09 -0800 References: To: users In-Reply-To: Message-Id: <4BDAF36B-DB33-4C2B-A8EC-D14D2584DE74@apache.org> X-Mailer: Apple Mail (2.3445.5.20) Are you see this on more than one host? Have you tried restarting it = and see if it goes over the maximum again? Here are are the stats I am seeing from a 7.1.2 server in production: [bcall@e10 ~]$ traffic_ctl metric match ram proxy.process.cache.ram_cache.total_bytes 31999999997 proxy.process.cache.ram_cache.bytes_used 31993472640 proxy.process.cache.volume_1.ram_cache.total_bytes 8000000000 proxy.process.cache.volume_1.ram_cache.bytes_used 7997441792 proxy.process.cache.volume_1.ram_cache.hits 32096586 proxy.process.cache.volume_1.ram_cache.misses 10833490 proxy.process.cache.volume_2.ram_cache.total_bytes 8000000000 proxy.process.cache.volume_2.ram_cache.bytes_used 7998451328 proxy.process.cache.volume_2.ram_cache.hits 34837324 proxy.process.cache.volume_2.ram_cache.misses 10840846 proxy.process.cache.volume_3.ram_cache.total_bytes 8000000000 proxy.process.cache.volume_3.ram_cache.bytes_used 7999866624 proxy.process.cache.volume_3.ram_cache.hits 32447086 proxy.process.cache.volume_3.ram_cache.misses 10697251 proxy.process.cache.volume_4.ram_cache.total_bytes 7999999997 proxy.process.cache.volume_4.ram_cache.bytes_used 7997786880 proxy.process.cache.volume_4.ram_cache.hits 30927240 proxy.process.cache.volume_4.ram_cache.misses 10826102 > On Feb 16, 2018, at 3:56 AM, Veiko Kukk wrote: >=20 > Hi, >=20 > We have strange situation with ATS 7.1.2 where RAM cache has grown = beyond set limits. >=20 > # /opt/trafficserver/bin/traffic_ctl metric match ram > proxy.process.cache.ram_cache.total_bytes 3112697856 > proxy.process.cache.ram_cache.bytes_used 4493088640 > proxy.process.cache.ram_cache.hits 1548 > proxy.process.cache.ram_cache.misses 1635443 > proxy.process.cache.volume_1.ram_cache.total_bytes 778174464 > proxy.process.cache.volume_1.ram_cache.bytes_used 1067949184 > proxy.process.cache.volume_1.ram_cache.hits 374 > proxy.process.cache.volume_1.ram_cache.misses 403206 > proxy.process.cache.volume_2.ram_cache.total_bytes 778174464 > proxy.process.cache.volume_2.ram_cache.bytes_used 1129483520 > proxy.process.cache.volume_2.ram_cache.hits 368 > proxy.process.cache.volume_2.ram_cache.misses 410164 > proxy.process.cache.volume_3.ram_cache.total_bytes 778174464 > proxy.process.cache.volume_3.ram_cache.bytes_used 1084551424 > proxy.process.cache.volume_3.ram_cache.hits 357 > proxy.process.cache.volume_3.ram_cache.misses 408656 > proxy.process.cache.volume_4.ram_cache.total_bytes 778174464 > proxy.process.cache.volume_4.ram_cache.bytes_used 1211104512 > proxy.process.cache.volume_4.ram_cache.hits 449 > proxy.process.cache.volume_4.ram_cache.misses 413417 >=20 > Relevant config parameters: > # /opt/trafficserver/bin/traffic_ctl config match ram > proxy.config.cache.ram_cache_cutoff: 16777216 > proxy.config.cache.ram_cache.size: -1 > proxy.config.cache.ram_cache.algorithm: 1 > proxy.config.cache.ram_cache.use_seen_filter: 1 > proxy.config.cache.ram_cache.compress: 0 > proxy.config.cache.ram_cache.compress_percent: 90 > proxy.config.ssl.server.dhparams_file: NULL > proxy.config.http2.max_frame_size: 16384 >=20 > I understand that, if set to -1, ATS will determine RAM cache size = automatically and that in our case would be = proxy.process.cache.ram_cache.total_bytes 3112697856 . >=20 > Why and how can it use more than that? >=20 > --=20 > Veiko >=20