On Wed, 2004-07-28 at 06:06, Jano wrote:
> Solved it changing the -Xmx128m to -Xmx256m.
> 
> I suppose this can be a general problem, I'm running stable without any 
> tweaks since a month or so.
> 
> In the good side, two minutes running and I can see all the activelinks, 
> where the previous build failed after many hours :)
> 

I upgraded promptly to 5085, 5086, and 5087.  All used more CPU time,
but eventually would finish.  Stackdump showed lots of biginteger stuff
while compute-bound.  Inserts were better than 5084, but retrieval much
worse.  RNF occurred in around 10 to 50% of all requests.  (Each request
was for a unique key).  Requesting peers-mode ocm seemed to trigger a
lot of CPU usage.

Switching back to 5084, I get much better performance on requests, with
very few RNF's.  Even fewer than I used to get, probably due to load
factors.  It appears that many stable nodes are switching back to 5084,
since I seem to recall that a day or two ago there were relatively few
5084 nodes.  (I didn't save the histogram then).

# Histogram of node versions in fred's Routing table
# Jul 28, 2004 8:25:46 AM
# nodes: 1556
Fred,0.5,STABLE-1.49,5063       1
Fred,0.5,STABLE-1.50,5070       1
Fred,0.5,STABLE-1.50,5083       1
Fred,0.5,STABLE-1.50,5084       692
Fred,0.5,STABLE-1.50,5085       164
Fred,0.5,STABLE-1.50,5086       615
Fred,0.5,STABLE-1.50,5087       81
unknown                         1


Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Reply via email to