build 524 has _serious_ performance issues! _____________________________ Current routingTime: 1098ms. Active pooled jobs: 16 (13.333334%) [QueryRejecting all incoming requests!] Available threads: 8 It's normal for the node to sometimes reject connections or requestsfor a limited period. If you're seeing rejections continuously the node is overloaded or something is wrong (i.e. a bug). Current estimated load: 88.588%. ________________________________
Perhaps you could say what changed in 522 -> 523, and whether it was really necessary. Up until the 523 release 'everything' was working just fine for most people, but now we're getting RNF & performance issues. BTW - I'm not trying to second-guess you on any of this, just something to consider. Sascha Noyes On Friday 25 October 2002 10:46 pm, Matthew Toseland wrote: > It turns out that the bug I just fixed with build 524/600 is fairly > serious. As in, it leads to constant RNFs when trying to insert, even > when using the desperation-mode-routing code I committed to the > development branch CVS. And initially RNFs when trying to fetch too. We > need a lot of nodes upgraded to 524 before 0.5.0 comes out. Thus we need > to release 0.5rc2 IMHO. The questions remaining are: > a) Do we include the desperation-mode-routing changes? This adds a > second pass in TreeRouting if the first one fails, in which it will try > backed off nodes and nodes with a low CP. > b) Do we up the minimum build, now or soon? > > It's far too late for me to be doing things this important, so I am > going to bed. But we need to deal with this tomorrow. _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
