"Houston, we have a problem..." Freenet's reliability and performance have been suffering terribly at present.
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: CHK at rUBq8clGt6jhX9Ro~rVQQDbV8s8NAwE,M1udAhD1eZYiG~kR9UC4zA 2) Using Freenet on another Windows system fails to get the file Again, htl=100 on requests - CLI and FProxy 3) FNP requests at high htls to other freenet nodes also fail to get the file. All this is happening to over 70% of my files. Every way, I just sit there waiting for 15 minutes to be told that I can't access a file I inserted at htl 100 from another node less than 24 hours ago. I'm interested to know of hard facts about success rates with data insertion/retrieval in Freenet - also, acceptable strategies for making files accessible. If I insert a file with htl = 100, and it can't be retrieved by other nodes (even at htl=100), then what's going on? I've got a shiny new GUI client that's working well and ready for release, but I'm reluctant to put it out there till I get an idea of what's going on with Freenet performance. Hey guys, if it gets any worse, then people might start calling Freenet 'vapourware'! A desperate part of me is sorely tempted to put up a daemon which continually milks inform.php and repeatedly inserts my files at low HTLs via FNP with every node it finds. Someone please help me back to sanity!!! David -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20010419/f2e5cf98/attachment.html>
