Hello,
I agree that it could be about VM/ATS settings.
Anyway, here are the info you wanted.
# grep thread /etc/trafficserver/records.config
CONFIG proxy.config.exec_thread.autoconfig INT 1
CONFIG proxy.config.exec_thread.autoconfig.scale FLOAT 1.50
CONFIG proxy.config.exec_thread.limit INT 2
Hi Baptiste,
In my opinion it's all about your VM/ATS settings.
Can you post these clues:
cat /proc/interrupts
cat etc/trafficserver/records.config | grep thread
cat etc/trafficserver/storage.config | grep dev
lshw -c disk -c volume
Cheers
JT
From: Jan-Frode Myklebust ;
To: ;
Subject: Re: Traf
On Wed, Jun 04, 2014 at 11:28:07AM +0200, Jean Baptiste Favre wrote:
> Hello,
> Each VM has 4GB memory.
>
> traffic_line -r proxy.config.cache.ram_cache.size gives 2147483648
I would consider increasing proxy.config.cache.ram_cache.size to at
least 3GB on your 4GB VMs. Assuming ATS will have bett
Hello,
Each VM has 4GB memory.
traffic_line -r proxy.config.cache.ram_cache.size gives 2147483648
Cache is splitted on 3 raw disks (sdb, sdc & sdd). Each disk is 10GB and
cache is full:
traffic_line -r proxy.process.cache.percent_full gives 99
I'm not sure how I can find cached entry number.
In
How much memory does the VM have? How much
proxy.config.cache.ram_cache.size have you given it? How much data are
you caching? How much is delivered to clients ?
-jf
Hi all,
I'm using Trafficserver 4.2.0 on Debian Wheezy, with raw disks as cache
on VMware virtual machines. Activity level is a bit less than 400
requests per seconds with a cache hit ratio greater than 99%.
On a regular basis, traffic_server process (ET_NET 0) starts to heavily
use CPU (more than
