I'm getting exactly this behaviour. Periodic very high CPU activity from slim.exe that lasts up to 20 minutes and stops the player. My library is about 25k songs. Having said that, although I'm trying to get it to use iTunes, I've not succeeded as yet, so I don't know if that is the issue, or not.
Tourne Healy Wrote: > Mine will peg out at 99% for 10-15 mins each time it does a rescan of > the itunes library. Even if I've just quit the iTunes and made no > changes > (IE: updates the time stamp of the xml file). It jumps up to 99% and > scans > through the whole library again. > > Meanwhile while that is happening, more than half the time, the music > will > cut out & the squeezebox will state "Can't find slimserver". > Sometimes > it will come back on and play for 1-2 seconds and they go dead for > another > 2 minutes. After the CPU goes back down to normal levels, the music > comes > back on. This happens wired or wireless. I used to have it check for > > iTunes > changes every hour, now I have it set to weeks to try and avoid that. > > This happened once in a while in the 5.x series but seem to happen now > > every > time it detects an iTunes change. It's getting to the point when I > can't even rely > on the squeezebox for a party anymore. Very disappointing. > > Is this the norm for users with huge libraries of music from now on? > > -Healy > > > On Apr 9, 2005, at 12:48 AM, Mark Bennett wrote: > > > The library scanning is much more CPU intensive than it was before. > > > > My collection of ~6k songs takes about 6 or 7 minutes to scan on > > a P4, 3.4GHz with 1GB RAM. Scaling that up to your music library > > size and CPU speed and it seems about right. This will happen > > at startup the first time, but it shouldn't need to do it again > > unless you've added music. > > > > On Fri, 2005-04-08 at 23:35 -0700, Healy wrote: > >> I've been having 99% CPU usage for long periods of time since > >> switching > >> to 6.0. Currently using > >> the 4/7 nightly with the same issues. On start up it pegs at 99% > CPU > >> for about 75 mins. > >> I have 26,000 songs on the server. I've removed all the plugins > >> except for: > >> > >> Datetime Screensaver > >> Rescan Music Library > >> Shoutcast > >> Save Playlist > >> iTunes > >> > >> It still seems to peg out.... > >> > >> Server is AMD 1.6ghz w/ 1.0gb ram, Debian Linux > >> Nothing else running except for sshd and basic init > >> functions. > >> > >> > >> > >> > >> On Mar 26, 2005, at 7:42 AM, Daryle A. Tilroe wrote: > >> > >>> Daryle A. Tilroe wrote: > >>>> Charles Stanton wrote: > >>>>> (We'll try this again). > >>>>> I am using the 3/23 nighly and from time to time on start-up, > >>>>> slim.exe > >>>>> will max out (96 - 99%) the CPU for 30 minutes or more before > >>>>> settling > >>>>> down. No new music has been added. I don't think it should be > >>>>> re-scanning. > >>>>> > >>>>> Generally it settles down within 5 minutes or so. > >>>>> > >>>>> The library is about 9K songs. The computer is PIII 933 MHz, > 512 > >>>>> RAM, W2K Pro. > >>>>> It is dedicated to the slimserver and musicmagic, which is also > >>>>> running. > >>>> I had something similar but possibly unrelated. For the last > week > >>>> and a half > >>>> I have been running the compiled 3/14 nightly under WinXPProSP1. > >>>> Tonight I noticed the service had gone "rogue" and was using all > >>>> available cycles. This was after a week of uptime and nowhere > near > >>>> a rescan and nothing was even playing. I just killed the service > > >>>> and > >>>> upgraded to 3/24. We shall see if it crops up again. > >>> > >>> OK It did it again and much faster (less than 36 hours); also I > don't > >>> think I even fired up the player. I currently suspect the RSS > >>> plugin. > >>> I turned it off and will wait a few days and see. > >>> > >> > >> -- Tourne _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
