Perhaps some of the performance loss you are seeing might be caused by ATS having to switch to a chunked transfer encoding when a transform is involved. What does cpu usage look like with and without a transform on your system?
Regards, Otto 2014/1/6 Uri Shachar <ushac...@hotmail.com> > On Mon, 6 Jan 2014 16:59:46 +0200 Roee Gil wrote > > Subject: Null transform slow down connection > snip > > 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 > > No - we currently do not have an option to collapse a transform once it > has started handling payload. > (Once you attach the transform to the transaction, you're committed) > > > 2. is it possible to reduce this number to some less then 50% bandwidth, > > and 20ms more? > > While all plugins incur some overhead - it shouldn't be anywhere close to > the numbers you are quoting > (I've just tried the null-transform plugin from trunk and I haven't seen a > noticeable perf impact). > > Which version are you running? Any changes in records.config? > > Cheers, > Uri
