> > No. As I said, NGRouting will be able to fix it. Look at your > > successTransferRate for the days when it was disabled. > > 4K-6K per second... With a sendData value of bwtween .13-.29 > > So its still not doing that well. Mind you, you did fix a bug that > might just help this... > > Maybe (just maybe) the best way to handle the massive number > of sends it to time them out if they do not achieve a high enough > rate. ie. accept a low sendData number when the sends do not > progress fast enough and we end up with a giant queue. Given > that there are lots of DSL type connections out there, IMO we > have to limit sends somewhere.
/me vomits. Please listen to what I am saying. It is not vital for ANY conceivable application of freenet that we get 30kB/sec on a typical single file transfer. Large files, streams and so on will be split. 6K/sec is fine. And the DSL conns only have a total of 16 anyway. And this sort of long term optimization should be done by NGRouting, because it can balance specialization against speed. > > Ed -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
