On Sat, Jan 12, 2002 at 04:39:14PM +0100, Sebastian Sp?th wrote: <> > Are we now restricting incoming and outgoing connections both by > MaxNodeConnections *and* maximumThreads? What`s the deal for both these > preferences if both do more or less the same (ok there might be some > more threads than connections, but basically it should correspond quite > well)?!
I don't normally read other peoples really long posts either, so I can't blame you, but you really should go back an read my post from the other day. GJ did not say that they now to the same thing: When the node is out of threads to use, it is in a bad way and cannot function well as node, wherefore it simply rejects incoming connections. When a node has read maxNodeConnections it simply feels it has reached the maximum number of connections is can comfortably keep open, and chooses to close one for every new one that comes in. As I noted before, the latter is in no way a choking or load balancing technique - it does nothing to discourage the node from receiving more traffic (GJ has implemented choking on the application level). In fact, I think that most nodes will find themselves with maxNodeConnections open all the time - and there really isn't anything wrong with that... > Can we do away with either one of these prefs? The number of threads necessary is probably a function of the number of connections that are allowed to be open, yes. We could consider defaulting maxThreads to the maximum of it's default and 1.5 * maxNodeConnections or something like that. > > Sebastian > > > _______________________________________________ > Devl mailing list > DevlOfreenetproject.org > http://lists.freenetproject.org/mailman/listinfo/devl -- Oskar Sandberg oskar at freenetproject.org _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
