|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
To: "Christopher L. Morrow" <christopher.morrow@mci.com>
Cc: nanog@nanog.org
In-Reply-To: Your message of "Tue, 25 Oct 2005 16:28:05 -0000."
<Pine.GSO.4.58.0510251627010.22139@parapet.argfrp.us.uu.net>
From: Valdis.Kletnieks@vt.edu
Date: Tue, 25 Oct 2005 13:06:52 -0400
Errors-To: owner-nanog@merit.edu
--==_Exmh_1130260012_3682P
Content-Type: text/plain; charset=us-ascii
On Tue, 25 Oct 2005 16:28:05 -0000, "Christopher L. Morrow" said:
> On Mon, 24 Oct 2005, Blaine Christian wrote:
> > Yea, but that's just me pinging everything and google and yahoo
> > fighting over who has the most complete list of x rated sites.
>
> and this probably depends greatly on the network, user-population,
> business involved. Is it even a metric worth tracking?
It's a fight for eyeballs, isn't it? Routing table hits caused by spidering
from search engines will give a good indication of what percent of the
address space the spiders are covering. Of course, you need views from
a number of places, and some adjusting for the fact that the webservers are
usually clumped in very small pockets of address space.
On the other hand, if it can be established that 80% of the routing table
is hit every <N minutes>, which would tend to argue against caching a very
small subset, but the vast majority of the routing table hits are just spiders,
that may mean that a cache miss isn't as important as we thought...
Anybody got actual measured numbers on how much of the hits are just spiders
and Microsoft malware scanning for vulnerable hosts?
--==_Exmh_1130260012_3682P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQFDXmYscC3lWbTT17ARAoVYAKCrL8syhNEglyTw87GSm3GSJ+x1CgCbBIif
xTVHnueuZM8yxQ7e1tyLO5g=
=M3ZH
-----END PGP SIGNATURE-----
--==_Exmh_1130260012_3682P--
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |