On Mon, Sep 01, 2003 at 03:59:42PM -0700, pineapple wrote: > This problem has been widely reported in the past, the > developers HOPE that nextgen routing will fix this.
Load imbalance? Yeah. However, it will be improved by NGRouting, if and when it works, and by NIOv2, when we implement it. > Right now your options are 1) put up with it, 2) run > an experimental version, 3) shut your node down or set > it to transient (if you do go transient, you'll have > to wipe out your node file to change your node's > identity because the network now knows about your > node). The problem seems to be caused too many > freenet.node.states.data.DataStateInitiator threads. > A suggestion to the developers; if there are too many > freenet.node.states.data.DataStateInitiator running, > just kill some, starting with the threads that have > been idle the longest. At least this way the node > will be able to fullfill some requests instead of > doing nothing for long periods. Ugh. Evil. Disgusterous. Low bandwidth node DoS. No, the solution is to implement more NIO so that the data transfers are asynchronous. This will also solve a possible low bandwidth DoS. This will be done after 0.6. But NGRouting *should* avoid routing to nodes with bazillions of transfers. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
pgp00000.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
