-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think when we have applications that explicitly rely on requesting keys that probably haven't been inserted yet, the proportion of successful requests is not a good measure of the network's effectiveness.
A good measure of the network's effectiveness is to manually insert keys at one node, and request those keys from another node, preferably one that is as far as possible from the first in the network topology, while monitoring the success rate. Ian. On 26 Apr 2006, at 06:12, Matthew Toseland wrote: > With Jogy's new code to show the counts of messages for individual > nodes, we have some rather depressing statistics once again. > > The apparent success rate on CHK requests is pretty bad... 1 in 3 at > best, 1 in 10 or worse is common... The success rate on SSK > requests is > even worse, but that's to be expected as that's mostly Frost. > > Possible explanations: > - Bug in the stats collection. > - People requesting files that haven't been inserted yet. > - Perverse network topology. > - Data not keeping up with location swaps. > - Load balancing/limiting not working. > > Any ideas on how to determine which of the above is correct? Or other > possible explanations? > > Generally feedback has been pretty good... I wonder if this might be > something like Frost requesting files that haven't been uploaded yet? > -- > Matthew J Toseland - toad at amphibian.dyndns.org > Freenet Project Official Codemonkey - http://freenetproject.org/ > ICTHUS - Nothing is impossible. Our Boss says so. > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFET6SQQtgxRWSmsqwRAriSAJ45Z8VxU4PULeXCf2TgdlZ0rygMhACfcxqu 7bG7Cwf+xAJcuBtlatyHtrs= =t5U3 -----END PGP SIGNATURE-----
