On Thu, Jul 03, 2003 at 06:37:25PM -0400, Todd Vierling spake thusly: > Sounds like broken code. While NIO can improve performance, it's certainly > not "critical" from the perspective of my long-running nodes. My nodes' > load rarely went above 50%.
How does Java normally handle dozens or hundreds of simultaneous connections? I've always done it with select() in C/Perl in Unix but Java doesn't have that for cross-platform reasons. Running potentially hundreds of threads at once does not yield good performance either. The general consensus seems to be that most nodes are overloaded (mine usually was before NIO) and reject connections and that is the cause of our routing woes. What do you consider to be the proper way to solve this problem? > points). These apps do rather intensive network I/O without NIO, and yet > I've experienced zero "broken" I/O problems in this codebase. Intensive network I/O can mean a number of things. Do they do hundreds of simultaneous connections? How? > After getting *a complete brush-off* from Ian himself when I did indeed > offer to help (in a quite extensive context), why the hell not? It's not as > if he gives a damn either. Well, Ian is Ian. You are of course welcome to fork the freenet code at the last stable pre-NIO release and implement your preferred solution. -- Tracy Reed http://ultraviolet.org
pgp00000.pgp
Description: PGP signature
