I really don’t know anything about C#, but are you sure the server can accept 1000 simultaneous requests and have all 1000 dispatched into the TestMethod? This sounds more like a server side bottleneck.
For example, I know with our Jetty based standalone services, the max would be 250ish (255 maximum threads, but some of the threads are used for the acceptors). For the older versions of jetty, the max would have been 16. Dan > On Dec 3, 2014, at 3:01 PM, user239 <[email protected]> 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. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
