Hi, I've been running the 6.2 betas for a while quite happily on a Win2003 SBS box with 512MB RAM. I have about 10,000 tracks and it was taking a few hours to rescan but it got there and there was nothing obvious missing.
I've since upgraded to the full 6.2 release and have now added about 10 new albums that I ripped to 192kbps MP3. I copied these albums into my music folder that is on a Linksys NSLU2 Network store (300GB USB2). I triggered a scan for new and changed files and after about 5 hours none of the new tracks turned up and the server was just eating RAM and CPU. The first new album I added was in the D's (Don Maclean) and it hadn't even got that far, it had managed about 2800 tracks but the count was stuck. I tried a full rescan and the same thing happened. Last night I deleted the SQL DB and upgraded to the 11/02 nightly and left it rescanning overnight. This morning it's got to the same point 2884 tracks but is now using 380 MB RAM and rising and 70-90% CPU. I'm now going to roll back to the last time I know this was working 6.2beta I think. So are there any ideas what could be causing this, has something been introduced in the final 6.2 that was not in the later betas? One thing to note, when I upgraded to the final 6.2 I did try the "keep server unswapped" setting, I changed this from the default of 30, to 15 and then to 10 but I couldn't see it making any difference to startup times when you first use the slimp3 or squeezebox 2 after a period of inactivity. This is currently set to 10. WOuld that make a difference? Any other ideas? cheers Steve -- stevekdavis _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
