The thing that takes a lot of CPU power is the DH exchange, and we need to do that fast, it can't be prioritized down. We'll look at cheaper key exchange methods when we overhaul that.
To the extent that the decrypt, authenticate, cache, re-encrypt cycle takes CPU time, throttling the bandwidth will have the effect of slowing that down as well. On Thu, Aug 24, 2000 at 11:20:56PM -0500, Brandon wrote: > > > possibly using the STOP and CONT signals as well if you need finer > > control during periods of high congestion. Yes, it's a hack, but > > it is probably portable between most all modern unixes... > > Signal processing in Java? I don't have a word to describe my feelings > on that. Something nasty. > > Plus it should be cross-platform if possible. If not then we need a > solution for each OS. > > Lowering the process priority might be okay. Might be tricky to get right. > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > -- \oskar _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
