Re:
http://mail-archives.apache.org/mod_mbox/trafficserver-dev/201210.mbox/%3ccafkfyq7kj_mgkcq5wx6umq46ujyxogfszgjvf_0fi7b90oj...@mail.gmail.com%3E
Hi Brian -
We are experiencing a similar issue here with EADDRNOTAVAIL occurring under low
load with no port exhaustion -
I was wondering if you
Hi,
We are looking at mitigating our system against any issues associated with long
term up time of ATS/ATM processes e.g. if any gradual memory growth.
To this end we want to close the ATS process to refresh it say every 2 days
(this time was used on Apache2 on previous project) -
Options
Thanks Leif,
Will take a look at that.
-Original Message-
From: Leif Hedstrom [mailto:zw...@apache.org]
Sent: 28 November 2012 15:40
To: dev@trafficserver.apache.org
Cc: Aidan McGurn; Alan M. Carroll
Subject: Re: question on TS refresh/restart
On 11/28/12 5:56 AM, Aidan McGurn wrote
Hi,
I see a performance dip on 3.2.0:
7% busy - 3.0.2
8% busy - 3.2.0
Under 10K load
Built with -O2 optimisation and configured as './configure
--enable-tproxy=force'.
records.config attached for each version -
Platform = Linux RHEL6.2/Intel Xeon
Latest traces I have:
(not much sticks out
Hi,
(I checked the forums - apologies if I missed this somewhere already) I had a
quick question on what the use case is for configuring ATS with attribute 'T'
i.e.
This attribute SERVER_PORT_BLIND_TUNNEL is only set when configured with 'T'
which implies HandleBlindTunnel the main tunnelling
