You seem to have totally ignored my previous email on this subject (despite replying to it!).
On Thu, Aug 07, 2003 at 11:51:09PM +0100, Toad wrote: > * Even when fixed, it led to it taking very long times to send messages. > This was apparently mainly because of messages being starved by > trailers. I made messages take priority over trailers, and limited > sends of trailers to available bandwidth, if there was some (it is > refreshed 10 times per second, so the chunks won't be too small). This > resulted in message send times being acceptably low, consistently. I > included a safeguard: after 2000ms, send jobs from trailers are > converted to the priority of messages (and sent to the end of the > queue). Also, negotiations are now throttled, with a priority higher > than messages. These are kludgy fixes for the general problem I described in my email earlier today - lets solve the problem properly rather than trying to patch up an overcomplicated and broken limiting mechanism with even more complexity. > We are also seeing very large numbers of trailing field sends on nodes > with the current code. Again, clearly explained by having a bunch of extremely slow connections, the reason for which (and solution for) I explained earlier today. > These could well be caused by trailers being of lower priority than > messages, and therefore starved. Theoretically my safeguard should hold. No, it is being caused by the basic problem I outlined earlier today. > One possible solution: I described the solution, if you don't like it - please explain why - don't just carry on as if I hadn't even mentioned it. Ian. -- Ian Clarke [EMAIL PROTECTED] Coordinator, The Freenet Project http://freenetproject.org/ Weblog http://slashdot.org/~sanity/journal _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
