Ok .. then I missunderstood. I thought you were using cxf aync http on
the server side.
As far as I know the async http transport is mainly useful at the server
side. There it can keep the thread count low.
On the client side there are normally never more than about 100 threads
for typical use cases.
Christian
On 03.12.2014 21:01, user239 wrote:
Christian, my server code is really simple, just waiting asynchronously for
1-2 seconds, so I don't expect it to be a bottleneck. Even when I send just
100 request, it's the same result: both transports show similar times.
(written in C#)
static Random rnd = new Random();
public async Task<Result> TestMethod(long id)
{
var result = new Result { Id = id };
// set some properties on "result"
await Task.Delay(rnd.Next(1000, 2000));
return result;
}
--
View this message in context:
http://cxf.547215.n5.nabble.com/Async-transport-performance-using-cxf-rt-transports-http-hc-tp5751832p5751875.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
