On May 25, 2015 12:23:39 AM GMT+02:00, Michael Osipov <micha...@apache.org> wrote: >Am 2015-05-24 um 14:25 schrieb Oleg Kalnichevski: >> [...] >>>> It all sounds very bizarre. I see no reason why HttpAsyncClient >without >>>> zero copy transfer should do any better than HttpClient in this >>>> scenario. >>> >>> So you are saying something is probably wrong with my client setup? >>> >> >> I think it is not unlikely. > >Guess what, I have changed the sample client to use HttpUrlConnection. >It instantly saturated the entire connection. Now I am completely >lost... > >I have tried 4.5 from branches, no avail. Then I have started to play >around with the builder options and disabled content compression. >Performance was off the charts. Full saturation: 11.4 MB/s. > >That made me wonder, I have redone the testing: > >1. Curl from a server with gigabit connection topped 30 MB/s. >2. Curl again but this time with Accept-Encoding. The speed drops to 7 >MB/s. Server is sending chunks. > >Compared to HttpClient, HC does a slightly better job when it comes to >compressed files. > >Looking at the source code and Javadocs, I do not see any option to >disable this by RequestConfig or via HttpContext attribute for this >single request. RequestContentEncoding class does not use HttpContext >variable in #process(). > >I am about to file an issue for that. WDYT? > Ah. Good catch. Makes sense. Please raise a Jira with a change request. I'll have to cancel RC1 vote, unfortunately, if we want this included in 4.5 release.
Oleg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
