On Friday 07 November 2003 05:27 pm, Toad wrote: > One radical solution: > Remove the code to reject queries when the bandwidth limit is exceeded! > > NGRouting can figure out when nodes are slow due to long term overload a > lot more easily and less alchemically than it can deal with query > rejections. Or so the theory goes. Am I smoking crack here?
Better solution: Limit each node to so many pending queries from you. Say 10. So if a node is already waiting on 10 returns form you, then if it sends another, that will be interpreted by your node as a request to also drop the first one. This way a node could know for certain that it would never have more than a certain number of pending requests. Then your node when processing these requests would have an idea when it's existing transfers would be done. For example if you have a request come in that is really good for one node and OK with another, but the good one is full, then the good one's time is the ETA of the first of the 10 pending + the estimated time for that key. _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
