Wow, oneswarm is one of the few p2p programs that doesnt die with 100% cpu
usage when I feed it with my 416 GB data in 58000 files that I wanna share
with the world. HOWEVER, I have noticed that firefox will use ALL memory
and die the swap death after a night when it displayed "Hashing.... 0% ..
100%" thing. If possible, try so oneswarm doesnt use up all the memory. In
the morning FF used 2.6 GB (I have 3 GB) memory and the box had a load of
55. Had to login remotely and kill firefox.
The other thing is I noticed is that it dies after about 2000 hashed files
with "java.lang.OutOfMemoryError: Java heap space". When I rised java
memory with -Xmx512m. It worked alot longer... but it died also.
In the end I used -Xmx1536m but it also died after a day or so. But it was
quite long time. It took over a WEEK to hash 58k files! Now its done, it
become 52700 torrents of it. I use -Xmx512m now because I have better use
of the memory then letting oneswarm get so much memory. What needs to be
fixed:
* Not use so much memory, something that can hash ALL files should be
default, so if -Xmx512m can hash unlimited amount of files, that should
be default and not -Xmx256m like it is now.
* Doesnt crash after a while when hashing files.
My sysinfo: oneswarm 0.6, firefox-3.0.10, linux 2.6, java version 1.6.0_13