On Thursday 15 May 2008 11:58, Jano wrote: > Matthew Toseland wrote: > > > On Wednesday 14 May 2008 10:32, Jano wrote: > >> Matthew Toseland wrote: > >> > >> > 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 > >> > >> See mine attached. This node has not been steadly 24/7 up as of late, which > > can > >> be more typical. It bounces a bit... > > > > What's the average uptime then? Has it been consistently up at certain times, > > or more downtime some weeks etc? > > This node used to be 24/7 up until recently when I started having HW problems. > The location is sampled every hour, not on changes (we could be missing resets > here). So, in the graph, you can see the downtimes as the periods without > samples. As you can see, the steady drifting and most jumps aren't caused by > downtime. > > I see big downtimes in > > 29-31/mar > 11-15/apr > 3-12/may > > There are no "scheduled" downtimes, this box is always on, unless some crash > takes it down until I'm back from work or week-end. > > I think I've solved the HW issues now, and I have a particular interest in > having this node up, so we can see more evolution in the future. > > > Your graph is really ugly. :( > > The spikes in times of good uptime are particularly noticeable. Would they be > randomization resets?
It looks like the spikes (long lines) result from long downtime, and when the node reconnects, it resets for some reason, presumably because its neighbours have moved on?? Is it pure opennet? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20080515/e4765d45/attachment.pgp>
