Closed GoogleCodeExporter closed 8 years ago
What speed is your internet connection? Were you downloading a lot of things in
the
background? How many minutes did you wait? The reason why I ask is this message:
> Congestion detected. Applied 5.00 multiplier to timeouts
5X is the maximum multiplier right now, which says to me that your internet
connection may be really slow, and that your DNS requests may be timing out.
In normal conditions, checking the availability of 3040 servers would only take
5
seconds. However, in the absolute worst case congestion with the default
settings,
this availability check could take 25.3 minutes! I'll admit, I had not thought
of this
possibility when setting the default timeouts. If you would like to speed up
the
availability and health checks, edit namebench.cfg to read:
health_timeout=2
thread_count=65
That should bring the time for this initial check for the 3040 servers down to
7.8
minutes. You could also uncheck the regional servers selection, which brings
the
number of servers to check down to 7 or 8. This could still be a bug with the
congestion code algorithm, but I'm not sure yet.
Original comment by tstromb...@google.com
on 17 Dec 2009 at 3:53
This is a Clearwire 4G connection, and I was running Namebench at 6 a.m. or so
and
not downloading anything. Just had my browser open -- not doing anything else.
For
what it's worth, my previous DSL service from ATT was very spotty, which is why
I
switched. I closed the terminal after 10 or 12 minutes when it didn't look like
anything was happening. I never got to the benchmarking point.
I made the namebench.cfg changes you recommended and unchecked the regional DNS
box.
The software ran fine -- took a couple of minutes to tell me Ultra DNS is 126
percent
faster.
I'll put the original settings back (you'll have to tell me what they are -- I
didn't
write them down) and let this run for as long as it takes.
Original comment by siegel...@gmail.com
on 17 Dec 2009 at 4:17
Do you mind testing namebench 1.1b1 to see if it has the same issue? It's
availability
checking has been completely overhauled.
Original comment by thomas.r...@gmail.com
on 3 Jan 2010 at 11:07
Original comment by thomas.r...@gmail.com
on 26 Jan 2010 at 8:49
Original issue reported on code.google.com by
siegel...@gmail.com
on 17 Dec 2009 at 1:26