Location churn: empirical data

Below are links to my node's location logs. A lot of the location churn is 
within roughly a slice of 10% of the keyspace, and the central signal is 
reasonably clean... but this degree of variation is going to cause problems 
with routing and especially data retention IMHO (on a network of several 
thousand nodes, with *at least* 1000 nodes online at a time). There were a 
whole bunch of resets during the week 19 April to 26 April, and on the 24th, 
RC2 was released; on May 8th, 0.7.0 was released. These may explain some but 
not all of the long jumps...

http://amphibian.dyndns.org/location.log.txt
http://amphibian.dyndns.org/locations.png

Random resets:
It is possible there were random resets before the first mentioned below, 
because we didn't log them until some time after we started logging 
locations.

20-Apr-2008 18:40:16 : 0.08100045552596624 (random reset)
21-Apr-2008 00:47:04 : 0.6871948987851273 (random reset)
21-Apr-2008 09:49:15 : 0.9095478261922363 (random reset from duplicated 
location)
23-Apr-2008 13:04:35 : 0.3044855058133896 (random reset from duplicated 
location)
23-Apr-2008 19:08:05 : 0.141007692250818 (random reset)
04-May-2008 14:33:46 : 0.18902390631238708 (random reset)

I am asking Oskar about this...

_______________________________________________
Tech mailing list
[email protected]
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIKgIxA9rUluQ9pFARAsF6AKCgX9ipfTEy+XbglPeUWifLcVdYQQCeKvxd
nFvAbUTgXzd09iEhlLxU3dI=
=MnN5
-----END PGP SIGNATURE-----