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.500000
CONFIG proxy.config.exec_thread.limit INT 2
CONFIG proxy.config.accept_threads INT 1
CONFIG proxy.config.cache.threads_per_disk INT 8
CONFIG proxy.config.ssl.number.threads INT 0
CONFIG proxy.config.task_threads INT 2

# grep dev /etc/trafficserver/storage.config
/dev/sdb
/dev/sdc
/dev/sdd

To avoid long output and format issue with mail, I used pastebin for
following command's results:

# cat /proc/interrupts -> http://pastebin.com/MvgpLB4S


# lshw -c disk -c volume -> http://pastebin.com/j2j5YnSX

Cheers,
Jean-Baptiste Favre

On 04/06/2014 14:59, jtomo...@yahoo.com.INVALID wrote:
> 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 <janfr...@tanso.net>; 
> To: <dev@trafficserver.apache.org>; 
> Subject: Re: TrafficServer and IO/Wait 
> Sent: Wed, Jun 4, 2014 10:45:27 AM 
> 
> 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 better knowledge about
> what to keep in memory than the linux page cache. 
> 
> And maybe give the VMs lots of more memory so that you can increase the
> ram_cache.size further.
> 
> I try to make sure ATS can keep everything in memory -- memory is cheap,
> disk IOPS is slow and expensive.
> 
> 
> 
>   -jf

Reply via email to