Hi, I think freenet is slow because its having problems finding data. The hit rates in 0.5 ranged around 5%. in 0.7 I see 2% on cache and 0% on store. We just are not finding data. My location shifts so fast that other nodes have no idea what is in my node's 8G store. I strongly suggest that we experiment with letting the store contents limit how far from the current location we can swap. This could easily be done with a tunable such that the effect could be turned off or could be made very strict. We could even use a feedback loop to find an optimal value with the store/cache hit rate being used to control just how strict we are. The idea would be to minimize the swapping limitation while maximizing the hit rate which would decrease the path length and hence the traffic.
In my case the node usually uses a good chunk (80-90%) of the bandwidth I give to it. I think the bandwidth limits work. I would agree that backout is probably not needed and think it would be a good idea to try with it turn off - again this would improve routing which I think is the core of 0.7 performance problems. Thanks Ed On November 30, 2007, Matthew Toseland wrote: > On Friday 30 November 2007 08:54, Florent Daigni?re wrote: > > > Obviously I expect the above will evolve over time. However, IMHO it > > > would > be > > > significantly better at matching demand to supply than the current > algorithm > > > while not sacrificing routing, and would therefore be a major improvement > in > > > performance, which is one of the most important problems Freenet needs to > > > deal with. > > > > You proposal is far away from tit-for-tat ... How do you prevent > > leachers from forgetting to send a "I want to process requests" flag ? > > Tit-for-tat can be layered on top of any sensible load management scheme (not > easily on the current system though). It's not something we need to deal with > right now. >
