Page 1 of 1

Search Index Issues

PostPosted: Wed Sep 09, 2009 5:38 am
by NiteFlame
Hi Everyone,

I am using Subsonic for a few months now and there have always been some issues with the search index, maybe someone has an idea how to fix it.

I am using Subsonic to stream music and video content. My music folder holds about 70 000 tracks and the video folder contains about 2 000 objects. The search index is set to be built every night at 1:00.

Yesterday i tried to find some tracks and subsonic told me that there are no matches. I manually re-built the search index and the tracks could be found after the rebuilding process. Tonight at 1:00 AM, the scheduled indexing task processed within about 3 mins, but the tracks that could be found yesterday are once more not available.

So what am I doing wrong? Is the music content folder too large? When I am creating a new directory within the video folder, it usually appears within Subsonic immediately, but not with the music folder. New music content is only presented after updating the search index (or not, as in case).

Any ideas would be very appreciated.

Re: Search Index Issue

PostPosted: Wed Sep 09, 2009 8:09 pm
by Subsonic Streamer
Me too, I have close to quarter million of music on 1TB storage just for the mp3s, but when I done a basic search or even advanced search it says no match found, however year back when I only has about 30 GB of music, all search of the music show up, maybe the search indexing isn't design for a music library this big?

Thanks in advance.

PostPosted: Wed Oct 07, 2009 3:46 am
by Subsonic Streamer
It's been awhile and no one wants to Help? This blows! Suck...

PostPosted: Wed Oct 07, 2009 4:39 am
by NiteFlame
I found out my search index gets much more complete when i increase the memory used by subsonic. I have increased it to 256 mb and it seems the index is near to complete. also the system seems to be much more stable now.

PostPosted: Wed Oct 07, 2009 5:02 pm
by donpearson
Subsonic Streamer wrote:It's been awhile and no one wants to Help? This blows! Suck...


Play nice now :oops:

PostPosted: Thu Oct 08, 2009 2:27 pm
by jeremyh
The index works fine for us on our fairly large sized library. We have 110,300+ songs spanning 600GB and it indexes fine for us.

I checked the memory usage and we are using 272 MB of the 400 MB it has reserved. So 256MB may be low. I suppose the search information could be cached and that would affect whether you get something returned real-time depending on the memory. You can try bumping up the memory and see what happens - it is a pretty easy thing to do. We have ours set to 128MB min 512MB max.