CPU at 100% when updating the search list (SOLVED)

[berthiggins]

Hi I have been using Subsonic for a while with collection of around 300GB
Recently I updated the collection to around 730 GB.
Now when it tries to update the search list the cpu goes to around 98% and stays there.
I have left it for a day without it coming to an end even if I stop subsonic and start it it goes to a high cpu immediately.
I have removed and re-installed Subsonic and all is well with the search function disabled.
This is a P3 1GHZ cpu with about 300MB of ram
it is running ubuntu server 8.10 .
I installed from the .deb file.
Do I need the more complex install type or is my server not "man" enough for the job with this collection?
Any ideas or hints appreciated.

[berthiggins]

Any Ideas anyone?

[mason]

im running a equal large collection on a amd 2400 be with 2gb ram, and subsonic takes a lot of power from it. i guess your little p3 is at it limits, but you can try and enlarge the java space maybe this will help

edit the subsonic.sh script and mod the following line :

SUBSONIC_MAX_MEMORY=64

I think 64mb was the default value, just try to edit it to 128 or maybe 196

[carbonrough]

.... going by the size of your collection, I'd feed Subsonic ~250MB of RAM once you've fed your under nourished Ubuntu

Peace

CR.

[berthiggins]

Thanks guys I will try that!

[delcypher]

If the high CPU usage is causing a problem then you can adjust subsonic's nice value (essentially adjusting the process's priority) to make your system more responsive.

My guess is that the problem will still persist until subsonic has finished building its search index.

See
http://www.linux.com/archive/feed/58638

[berthiggins]

Thanks everyone
I have increased memory on java to 256 MB ( found I had 512 rather than 300 )
I hver reniced subsonic to +12 we shall see!

[berthiggins]

Thanks Guys that worked! I now have a search index.
I think the renice was the main thing as I watched the index built with a tail -f on the subsonic.log and monitored the system state with top .
the java memory usage was never very high but the cpu usage kept nice and low.

Thanks for your help!