On Thursday 19 April 2001 06:37, David wrote: > > "Houston, we have a problem..." > > Freenet's reliability and performance have been suffering terribly at > present. This isn't the way things look in my world. It seems that reliability is actually getting better. I can find most *new* files most of the time.
Here are some guesses as to factors which might explain our differing experiences. 1) I have a well established non-transient node. I insert and request lots of stuff from it daily. I think this is probably the most important factor. 2) I am running Linux. Since I think most of the developpers also run *nix this is where I would expect the code to be most robust. Also, it doesn't crash. 3) I use GetFiles to pre-fetch new or troublesome files. It automatically retries failed requests. My guess as to why this helps is that requests time out while data is still in the process of moving toward the node where it was requested. The next time you do the request there's a better chance that the data will have arrived, especially if there's a delay between request attempts. ever the contrarian -- gj > > I was unaware of the issues till I created a new Windows installation on a > fresh partition, and installed a new Freenet on it. While I'm running > Freenet from this Windows partition, my main node (and my datastore) is (of > course) offline. > > Specifically, most keys I insert, even with htl 100, can't be retrieved > from other nodes, not even with htl=100. > > The test I've done is: > > 1) Insert, at htl=100, a small GIF file, key is: I don't think that this is helping you. I seldom use and insert htl greater than 50. > CHK at rUBq8clGt6jhX9Ro~rVQQDbV8s8NAwE,M1udAhD1eZYiG~kR9UC4zA I retrieved this no problem in fproxy with the default htl -- gj P.S: C.E. I haven't rebuilt fred in the last 2 days. --
