> From my personal experience a decent blocking HTTP client can be
> expected to outperform a decent non-blocking HTTP client by 50 to 100%,
> but such a massive difference does look very suspicious. My guess,
> though, that the way pages are being processed can be a limiting factor
> more more tha
Just to complete the discussion, I finally set up the async client properly
and it's pulling around 5000p/s, whereas the blocking client (with 1000
threads) has peaks of 1-15000 p/s, and average around 8000p/s, which is
in line with your predictions.
--
View this message in context:
http://
Did you try to use empty string domain (not null) and let server to use
it's default? It might help. Just for testing purposes. Simply the end user
should decide if he uses domain or not as he has the knowledge of an
environment.
Bronislav
2013/2/1 Oleg Kalnichevski
> On Fri, 2013-02-01 at 07:0
We had also similar problem with proxy NTLM authentication and we have to
use jcifs for fixing of this problem. The bug
https://issues.apache.org/jira/browse/HTTPCLIENT-1080 is fixed now so I
will do some tests if it has really gone.
I think there might be some issues with domain. I would try to p
