Hi.
Recently I was working with the Tomcat Servlet engine, my servlet was
generating gifs on the fly. It was able to process about 30-50
requests/second on a standard PC ( 500Mhz ). Taking that into account I
guess freenet should handle over 100 requests/second, because most
requests (when
Roman Bednarek [EMAIL PROTECTED] writes:
Hi.
Recently I was working with the Tomcat Servlet engine, my servlet was
generating gifs on the fly. It was able to process about 30-50
requests/second on a standard PC ( 500Mhz ). Taking that into account I
guess freenet should handle over 100
I recommend you try just doubling the maxThreads setting in your
freenet.conf. This should provide a similar result. We need a way to
work out the optimal load maximum at configuration time... or adjust it
dynamically.
On Wed, Jun 26, 2002 at 05:31:01PM -0700, Tril wrote:
I setup a node on a
If the diff below is complete, your changes have done nothing other than
remove the notification to you when incoming connections are being
rejected. The actual rejecting of connections is not handled by
rejectingRequests(). If you'd like to see what actually happens when
your node ignores the
On Wednesday 26 June 2002 23:30, Pascal wrote:
The reason these limits are there is to keep badly behaved nodes from DOSing
the rest of freenet. There were situations where nodes would try to send
hundreds of times more requests than they could answer.
It isn't a good idea for nodes to try
That would make sense, unfortunately that's not how it's currently
implemented. With default values, all outboundRequestLimit does is make
the node QRej requests not in it's DS or FT if it has sent more than 60
requests in a minute. It doesn't care how many requests the node has
received. Nor
