> does "CONFIG proxy.config.http.chunking_enabled INT 1" does that make any > changes in the transform? > in any case, I see the CPU spikes, but nothing dramatic."
I suspect that disabling chunking will make ATS disable keep alive. It will indicate the end of the transformed stream to the user-agent by sending a connection: close header. So, this might reduce cpu overhead as far as ATS is concerned, at the cost of reducing performance in another area (dropping keep alive). Otto On 22 Jan 2014, at 12:43, roee gil <roe...@gmail.com> wrote: > first of all ,thanks to you all, > > I'm working with ATS 3.2.5 in my record config I could not see your mail > till now, I accidentally archived them > > Uri, > I tested it again now, and I see that the latency is almost the same, so > will put that a side. > and no, there are no dramatic changes in the record config > > Otto, > does "CONFIG proxy.config.http.chunking_enabled INT 1" does that make any > changes in the transform? > in any case, I see the CPU spikes, but nothing dramatic. > > Leif, > I added "proxy.config.http.chunking.size INT 64k" > so I added it, it seems to improve how much we lost (about 10% > improvement), still lost is still huge. > > BR, > Roee > > > On Mon, Jan 6, 2014 at 4:59 PM, roee gil <roe...@gmail.com> wrote: > >> Hi all, >> >> I'm trying to understand what are the trade off when I use transform. >> so I did a speed test at this site: http://www.speedtest.net/ >> >> and checked it without ATS, with ATS with no plugins and finally ATS with >> null transform plugin. >> >> between with and without ATS, I had not change at all, but when I added >> the null transform, I had 50% of bandwidth (15MB instead of 30MB) and 20ms >> more latency (3ms was without plugin) >> >> I have 2 question in this subject >> >> 1. is it possible to stop a transform, and let the ATS continue the >> session without the plugin >> 2. is it possible to reduce this number to some less then 50% bandwidth, >> and 20ms more? >> >> BR, >> Roee >>
