-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So basically, only an insert can flush out inserted data, and only requests can flush out requests? I can see how that would help.
How do we find the right ratio between the sizes of the two datastores? Ian. On 30 Jun 2006, at 13:12, Matthew Toseland wrote: > 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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEpYb4QtgxRWSmsqwRAluAAJ9ThsKIwilEYy5C/U9qiGFtQjN2OQCfV70Z uh+XV22y61GcqBg8QBKgGYU= =HzBG -----END PGP SIGNATURE-----
