PDA

View Full Version : Hourly dropouts



Richie
2005-02-17, 16:12
Hi,

Does anyone know if there are any plans to address Bug 826. This is
the one where there are hourly dropouts due to 100% CPU activity
caused by slim.exe.

I'm also suffering from this problem and get at least a couple of
dropouts a day when playing flac tracks. It's starting to get really
irritating. Other than that I reckon the Squeezbox is one of the best
gadgets I've ever brought. I'd like to buy a couple more but would
prefer that this was fixed first.

I haven't been able to find out much information about it. I'd gone to
the trouble of moving the server from an XP machine to a linux server
and buying a new network switch before I found the bug mentioned here.
Process logging on the XP machine confirmed that it is definitely
slim.exe causing the CPU spike every hour. I have experienced the
dropouts under Suse Linux as well but I don't have the knowledge to
figure out whats causing it there, since then I've moved back to XP.

Just in case it's relevant: I have a library of about 8k flac tracks
on an Athlon 1.4GHz machine with 768MB of RAM running XP SP2 and
5.4.0.

Thanks for any help

Richard

Aaron Zinck
2005-02-17, 16:16
"Richie" wrote
> Hi,
>
> Does anyone know if there are any plans to address Bug 826. This is
> the one where there are hourly dropouts due to 100% CPU activity
> caused by slim.exe.
>
> I'm also suffering from this problem and get at least a couple of
> dropouts a day when playing flac tracks. It's starting to get really
> irritating. Other than that I reckon the Squeezbox is one of the best
> gadgets I've ever brought. I'd like to buy a couple more but would
> prefer that this was fixed first.
>
> I haven't been able to find out much information about it. I'd gone to
> the trouble of moving the server from an XP machine to a linux server
> and buying a new network switch before I found the bug mentioned here.
> Process logging on the XP machine confirmed that it is definitely
> slim.exe causing the CPU spike every hour. I have experienced the
> dropouts under Suse Linux as well but I don't have the knowledge to
> figure out whats causing it there, since then I've moved back to XP.
>
> Just in case it's relevant: I have a library of about 8k flac tracks
> on an Athlon 1.4GHz machine with 768MB of RAM running XP SP2 and
> 5.4.0.
>
> Thanks for any help
>
> Richard

Richard,

If you're willing to use the source distro you could follow this tip:
http://lists.slimdevices.com/archives/discuss/2004-November/038163.html

Richie
2005-02-18, 00:11
Thanks. I had seen that. I changed the value from 3600 to 600000 and
it made no difference. However, I'm unsure what you mean by source
distro, I'm just using the executable (SlimServer_v5.4.0.exe) I
downloaded off the Slim download page.

Richard


On Thu, 17 Feb 2005 18:16:52 -0500, Aaron Zinck <azinck3 (AT) ufl (DOT) edu> wrote:
> "Richie" wrote
> > Hi,
> >
> > Does anyone know if there are any plans to address Bug 826. This is
> > the one where there are hourly dropouts due to 100% CPU activity
> > caused by slim.exe.
> >
> > I'm also suffering from this problem and get at least a couple of
> > dropouts a day when playing flac tracks. It's starting to get really
> > irritating. Other than that I reckon the Squeezbox is one of the best
> > gadgets I've ever brought. I'd like to buy a couple more but would
> > prefer that this was fixed first.
> >
> > I haven't been able to find out much information about it. I'd gone to
> > the trouble of moving the server from an XP machine to a linux server
> > and buying a new network switch before I found the bug mentioned here.
> > Process logging on the XP machine confirmed that it is definitely
> > slim.exe causing the CPU spike every hour. I have experienced the
> > dropouts under Suse Linux as well but I don't have the knowledge to
> > figure out whats causing it there, since then I've moved back to XP.
> >
> > Just in case it's relevant: I have a library of about 8k flac tracks
> > on an Athlon 1.4GHz machine with 768MB of RAM running XP SP2 and
> > 5.4.0.
> >
> > Thanks for any help
> >
> > Richard
>
> Richard,
>
> If you're willing to use the source distro you could follow this tip:
> http://lists.slimdevices.com/archives/discuss/2004-November/038163.html
>
>

Jason Holtzapple
2005-02-18, 07:18
Richie wrote:
> Thanks. I had seen that. I changed the value from 3600 to 600000 and
> it made no difference. However, I'm unsure what you mean by source
> distro, I'm just using the executable (SlimServer_v5.4.0.exe) I
> downloaded off the Slim download page.

No, that tip won't work for the exe. On Windows you'll need to download
the source .zip and use the ActiveState perl environment to run the
server. That's about all I know as I don't run on Windows.

> On Thu, 17 Feb 2005 18:16:52 -0500, Aaron Zinck <azinck3 (AT) ufl (DOT) edu> wrote:
>
>>"Richie" wrote
>>
>>>Hi,
>>>
>>>Does anyone know if there are any plans to address Bug 826. This is
>>>the one where there are hourly dropouts due to 100% CPU activity
>>>caused by slim.exe.
>>>
>>If you're willing to use the source distro you could follow this tip:
>>http://lists.slimdevices.com/archives/discuss/2004-November/038163.html

Aaron Zinck
2005-02-18, 07:19
"Richie" <gibbering.idiot (AT) gmail (DOT) com> wrote in
message news:cf07d809050217231116f11ba3 (AT) mail (DOT) gmail.com...
> Thanks. I had seen that. I changed the value from 3600 to 600000 and
> it made no difference. However, I'm unsure what you mean by source
> distro, I'm just using the executable (SlimServer_v5.4.0.exe) I
> downloaded off the Slim download page.
>
> Richard

Richard,
Sorry--honestly hadn't looked for that file myself, was just quoting what
that poster had said. I've never had to mess with this so I'm afraid I
can't offer any more help.

-Aaron

Richie
2005-02-18, 10:58
OK, I'll give that a try.

What impact will changing this setting have on the performance of the
SlimServer?

Richard


On Fri, 18 Feb 2005 15:06:36 -0000, Ben Cook <ben (AT) bencook (DOT) net> wrote:
> I experience this issue as I have a low poer server (Via C3 700MHz). To fix
> it (Windows server) turn off the hourly cache:
>
> In Wordpad open C:\Program Files\SlimServer\server\Slim\Music\Info.pm
> Search for "sub saveDBCacheTimer"
> Comment out the two lines in this sub with the # symbol. The sub should look
> like:
>
> sub saveDBCacheTimer {
> # saveDBCache();
> # Slim::Utils::Timers::setTimer(0, Time::HiRes::time() + $dbSaveInterval,
> \&saveDBCacheTimer);
> }
>
> I'd love to be able to do this from the web interface, it's a bit of a pain
> having to do it each time I install the software.
>
> Hopefully this will help you.
>
> Ben.
>
>
> > -----Original Message-----
> > From: discuss-bounces (AT) lists (DOT) slimdevices.com
> > [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com]On Behalf Of Richie
> > Sent: 17 February 2005 23:13
> > To: Slim.Discuss
> > Subject: [slim] Hourly dropouts
> >
> >
> > Hi,
> >
> > Does anyone know if there are any plans to address Bug 826. This is
> > the one where there are hourly dropouts due to 100% CPU activity
> > caused by slim.exe.
> >
> > I'm also suffering from this problem and get at least a couple of
> > dropouts a day when playing flac tracks. It's starting to get really
> > irritating. Other than that I reckon the Squeezbox is one of the best
> > gadgets I've ever brought. I'd like to buy a couple more but would
> > prefer that this was fixed first.
> >
> > I haven't been able to find out much information about it. I'd gone to
> > the trouble of moving the server from an XP machine to a linux server
> > and buying a new network switch before I found the bug mentioned here.
> > Process logging on the XP machine confirmed that it is definitely
> > slim.exe causing the CPU spike every hour. I have experienced the
> > dropouts under Suse Linux as well but I don't have the knowledge to
> > figure out whats causing it there, since then I've moved back to XP.
> >
> > Just in case it's relevant: I have a library of about 8k flac tracks
> > on an Athlon 1.4GHz machine with 768MB of RAM running XP SP2 and
> > 5.4.0.
> >
> > Thanks for any help
> >
> > Richard
> >

nico-kw-slim.950fa0@gianniotis.org
2005-02-18, 16:32
Hi chaps,

I am the original poster of that bg report and I found the solution
proposed by Jason (changing the save interval) solved the problem for
me. That was with the 5.3.x release. Since then I have upgraded to
5.4.0 and the hourly dropouts have returned, so I'm planning to make
the same change again in the 5.4.0 codebase.

FWIW, I am running the source distribution on Solaris. That means I
run slimserver.pl and I actually have the file Music/Info.pm present
in the slimserver home directory. This is the file which I edited last
time, which solved the problem.

HTH,
Nico

Aaron Zinck writes:

> "Richie" <gibbering.idiot (AT) gmail (DOT) com> wrote in
> message news:cf07d809050217231116f11ba3 (AT) mail (DOT) gmail.com...
>> Thanks. I had seen that. I changed the value from 3600 to 600000 and
>> it made no difference. However, I'm unsure what you mean by source
>> distro, I'm just using the executable (SlimServer_v5.4.0.exe) I
>> downloaded off the Slim download page.
>>
>> Richard

> Richard,
> Sorry--honestly hadn't looked for that file myself, was just quoting what
> that poster had said. I've never had to mess with this so I'm afraid I
> can't offer any more help.

> -Aaron



>

Richie
2005-02-19, 14:06
Well, I've made a couple of changes now.

1. Disabled the SlimServer service
2. Installed ActivePerl
3. Modified info.pm as suggested

Now, clicking on slimserver.pl in the original installation folder
appears to get SlimServer up and running with no problem. Its just a
matter of waiting and listening to see if this has cured the hourly
dropouts.

Thanks for all the help so far.

Richard


On 19 Feb 2005 10:32:21 +1100, nico-kw-slim.950fa0 (AT) gianniotis (DOT) org
<nico-kw-slim.950fa0 (AT) gianniotis (DOT) org> wrote:
> Hi chaps,
>
> I am the original poster of that bg report and I found the solution
> proposed by Jason (changing the save interval) solved the problem for
> me. That was with the 5.3.x release. Since then I have upgraded to
> 5.4.0 and the hourly dropouts have returned, so I'm planning to make
> the same change again in the 5.4.0 codebase.
>
> FWIW, I am running the source distribution on Solaris. That means I
> run slimserver.pl and I actually have the file Music/Info.pm present
> in the slimserver home directory. This is the file which I edited last
> time, which solved the problem.
>
> HTH,
> Nico
>
> Aaron Zinck writes:
>
> > "Richie" <gibbering.idiot (AT) gmail (DOT) com> wrote in
> > message news:cf07d809050217231116f11ba3 (AT) mail (DOT) gmail.com...
> >> Thanks. I had seen that. I changed the value from 3600 to 600000 and
> >> it made no difference. However, I'm unsure what you mean by source
> >> distro, I'm just using the executable (SlimServer_v5.4.0.exe) I
> >> downloaded off the Slim download page.
> >>
> >> Richard
>
> > Richard,
> > Sorry--honestly hadn't looked for that file myself, was just quoting what
> > that poster had said. I've never had to mess with this so I'm afraid I
> > can't offer any more help.
>
> > -Aaron
>
> >

Richie
2005-02-21, 13:14
The server has now run for two days without any glitches. Logging the
perl.exe process shows that the hourly CPU spikes have stopped.

Thanks again for the help.

One last question, is there any downside to disabling writing the tag
cache to disk?

Richard


On Sat, 19 Feb 2005 21:06:07 +0000, Richie <gibbering.idiot (AT) gmail (DOT) com> wrote:
> Well, I've made a couple of changes now.
>
> 1. Disabled the SlimServer service
> 2. Installed ActivePerl
> 3. Modified info.pm as suggested
>
> Now, clicking on slimserver.pl in the original installation folder
> appears to get SlimServer up and running with no problem. Its just a
> matter of waiting and listening to see if this has cured the hourly
> dropouts.
>
> Thanks for all the help so far.
>
> Richard
>
> On 19 Feb 2005 10:32:21 +1100, nico-kw-slim.950fa0 (AT) gianniotis (DOT) org
> <nico-kw-slim.950fa0 (AT) gianniotis (DOT) org> wrote:
> > Hi chaps,
> >
> > I am the original poster of that bg report and I found the solution
> > proposed by Jason (changing the save interval) solved the problem for
> > me. That was with the 5.3.x release. Since then I have upgraded to
> > 5.4.0 and the hourly dropouts have returned, so I'm planning to make
> > the same change again in the 5.4.0 codebase.
> >
> > FWIW, I am running the source distribution on Solaris. That means I
> > run slimserver.pl and I actually have the file Music/Info.pm present
> > in the slimserver home directory. This is the file which I edited last
> > time, which solved the problem.
> >
> > HTH,
> > Nico
> >
> > Aaron Zinck writes:
> >
> > > "Richie" <gibbering.idiot (AT) gmail (DOT) com> wrote in
> > > message news:cf07d809050217231116f11ba3 (AT) mail (DOT) gmail.com...
> > >> Thanks. I had seen that. I changed the value from 3600 to 600000 and
> > >> it made no difference. However, I'm unsure what you mean by source
> > >> distro, I'm just using the executable (SlimServer_v5.4.0.exe) I
> > >> downloaded off the Slim download page.
> > >>
> > >> Richard
> >
> > > Richard,
> > > Sorry--honestly hadn't looked for that file myself, was just quoting what
> > > that poster had said. I've never had to mess with this so I'm afraid I
> > > can't offer any more help.
> >
> > > -Aaron
> >
> > >

kdf
2005-02-21, 13:33
Quoting Richie <gibbering.idiot (AT) gmail (DOT) com>:

> The server has now run for two days without any glitches. Logging the
> perl.exe process shows that the hourly CPU spikes have stopped.
>
> Thanks again for the help.
>
> One last question, is there any downside to disabling writing the tag
> cache to disk?

longer startup time, since it has to rescan your library every time you start
the server.

however, the 6.0 development is progressing well and uses a DB backend. A lot
of work is going into optimising all accessing and writing of the database so
that those hourly dropouts will not be an issue.

-kdf

Kirk Ferguson
2005-02-21, 13:45
Hello, all.

Just a quick question: Are the system memory requirements under version 6.0 as
high as under the 5.4 versions?

I have about 23,000 songs, and find that nearly 200M of ram is allocated to the
slimserver process under Linux on a P4 system.

I've had the server run out of memory and crash a number of times during library
scans.

I upgraded the server from 512M to 1GB recently, and seem to be more stable
since, but I'm planning ahead and wondering if I'll need even more RAM in the
future...

Thanks,

Kirk Ferguson

Dan Sully
2005-02-21, 13:47
* Kirk Ferguson shaped the electrons to say...

>Just a quick question: Are the system memory requirements under version 6.0 as
>high as under the 5.4 versions?

No - they will be much lower.

>I have about 23,000 songs, and find that nearly 200M of ram is allocated to the
>slimserver process under Linux on a P4 system.

6.0 has a much more steady-state of memory usage, depending on your OS, but
should be in the 30-50M ballpark.

-D
--
<Djall> and I also learned that a meat vortex takes meat away from you.

kdf
2005-02-21, 13:48
Quoting Kirk Ferguson <kferguson (AT) students (DOT) cncc.edu>:

> Hello, all.
>
> Just a quick question: Are the system memory requirements under version 6.0
> as
> high as under the 5.4 versions?
>
> I have about 23,000 songs, and find that nearly 200M of ram is allocated to
> the
> slimserver process under Linux on a P4 system.

10,468 songs works out to about 51-55M after scanning for me, depending on how
many importers I've added at the time.

-kdf

Kirk Ferguson
2005-02-21, 14:44
Quoting Dan Sully <dan (AT) slimdevices (DOT) com>:

> * Kirk Ferguson shaped the electrons to say...
>
> >Just a quick question: Are the system memory requirements under version 6.0
> as
> >high as under the 5.4 versions?
>
> No - they will be much lower.
>
> >I have about 23,000 songs, and find that nearly 200M of ram is allocated to
> the
> >slimserver process under Linux on a P4 system.
>
> 6.0 has a much more steady-state of memory usage, depending on your OS, but
> should be in the 30-50M ballpark.
>
Thanks. I suspected as much. Guess I'd better find version 6.0 and get it
installed.

Kirk