YoKenny said:
You obviously have something very wrong with your system. If you
are using Win2K/XP then disable the DNS Service. I'm using almost
20,000 entries at 581K with no slowdown. Browsing with or without
the HOSTS file is the same time. Faster with actually because the
ads are not retrieved and eDexter with my customized images shows it
is working.
My system is not 2K/XP. The slowdown I mentioned may have been due to
any number of factors associated with the spyware rubbish I'd been
infected with, which has now been eradicated, together with the
slowdown. Nothing appears to be "very wrong" or even a bit wrong with my
system now.
My point about the hosts file remains though. Unless the fundamental
mechanism used to access the hosts file has changed in more recent
Windows versions, it represents a most inefficient way of redirecting
domains to localhost. Some fairly extensive testing I was involved in
(comparing hosts performance against a junk filtering local proxy)
showed that hosts loads into memory from disk, *every time* it is
accessed. It can't possibly take "the same time" with or without the
hosts file, even though you may perceive it as such. Naturally, overall
browsing may well (and should) show a noticable improvement, with less
junk being downloaded. But this is apples & oranges, since now we're
comparing local I/O disk reads with internet downloading.
In addition, hosts is searched sequentially (slowest method possible)
and it doesn't operate with any pattern matching or wildcard support (at
least when used on its own). Compared with memory resident proxies etc.
which have rather "smarter" methods of identifying and blocking junk,
hosts is a very inefficient option. It was never designed to contain
massive numbers of "blocked" sites, but rather provide a list of
(relatively few) numerical IP addresses corresponding to IP host names,
thereby avoiding DNS lookup and, in theory, speeding things up. If you
look at the file hosts.sam, it will give you some idea of its intended
usage.