?= Date: Mon, 16 Jun 2003 12:02:31 -0400 User-Agent: KMail/1.5.9 Cc: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> X-KMail-Link-Message: 139108127 X-KMail-Link-Type: reply MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <[EMAIL PROTECTED]> Status: RO X-Status: Q X-KMail-EncryptionState: X-KMail-SignatureState: X-KMail-MDN-Sent:
On June 16, 2003 08:21 am, Toad wrote: > We ABSOLUTELY MUST NOT implement NGrouting, or edt's new CP algorithm, > until NIO is in. Because we do not want to introduce a bias favouring > nodes with connections already open, when we have the current situation > where nodes cannot keep anything like enough connections open. GJ just > fixed a bug like this not long ago, it is a REALLY BAD THING. It causes > network load handling to be even worse than it is now. Toad I already agreed on irc not to put this in without your ok. Stating that something is bad without testing it is not the way to improve things. You are worried that my changes (and NG) will be biased towards cached connections. Fine. I will extract the part of my changes that instruments routing, without changing it so we can see just what bias my code introduces - if any. Once we have measured things _then_ we can decide if the changes are a good thing. That brings up an interesting point. How do we measure the efficiently of routing. What metrics would make sense to track and why? Ed _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
