Oskar tells me that the following will work a lot better than our current strategy for storing data, according to his simulations:
We have a separate cache and store. Both are LRU. The cache stores everything which passes through the node (possibly excluding locally originated traffic on more paranoid nodes). The store stores ONLY data from inserts, and it only stores it if the HTL was reset on that node because it was a new best location for the request. (Is this right Oskar?). The store would probably be larger than the cache. Successful requests will occasionally turn into inserts. We cannot store data to the store on requests because many requests are satisfied a long way away from the target. Most DHTs include a two level store, as oskar pointed out. The best results on a static network come from storing it only on the single node closest to the target; storing it on the 3 nodes closest to the target seemed to work well on a dynamic network. But that's hard to implement, hence the suggested solution of storing the data on the "peaks". It would be a good thing to get this implemented in the near future. But first we have to agree on it. -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20060630/253b6a14/attachment.pgp>
