On Thu, Jul 03, 2003 at 11:20:09PM -0500, Tom Kaitchuck wrote: > > Oh, and any such solution have to stand up to the ability of having 500 > > open connections under linux with less than 50% cpu usage on 1 to 2 Ghz > > x86 cpus and maintain routingTime averages of less than 30ms. Because > > that's exactly what 1.4.[1/2] with nio does now. > > > > P.S. FYI, 1.4.1 & 2 are NPTL-enabled. > > NOT ON MY BOX! I have even gone so far as to limit myself to 128 connections > and my CPU useage is still averaging more than 75% useage, and is at 100% a > lot! Of course it is Niced so it doesn't interfere much, but it DOES suck up > LOTS of CPU. (I have a 1.53Ghz Athlon under Linux.) My load has been > constantly over 90% ever sense 597 and my load is consistently 10x the > network average. NIO has changed nothing for me except make Freenet a lot > faster, and my regular Internet is a lot slower because Freenet uses so much > bandwidth, and is very chatty. (and limiting doesn't seem to help)
Which side of limiting? Everything I have heard and tested says outbound bandwidth limiting works. Is this contrary to your experience? > > I hate to complain. But there is obviously still something very broken. So it > would be good to sort all that out before making any definitive claims as to > how much it has improved things. Yes, load balancing still has some way to go. Some nodes end up serving a disproportionate share of traffic. Hopefully this will improve as more NIO nodes become available, and improve further with NGrouting. But, how much outbound bandwidth do you have? Most ubernodes even now are those with unusually high outgoing bandwidth... -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
pgp00000.pgp
Description: PGP signature
