PDA

View Full Version : Performance &/or Stability Issues with SlimServer 5.1.5 on Win XP Pro SP1



Hugh Hempel
2004-05-25, 15:02
Greetings,



I am a relatively new user and absolutely love the Squeezebox and Slim
Server! When they are working.



My main issue is most probably related to the size of my collection (about
57,000 MP3s) and/or the organization of the collection and/or the
implementation of my MP3 tags.



Currently, I can not get SlimServer to run for more than a few hours. It
appears to me that when the server starts and begins to rescan the MP3
library I run out of memory (about 90-120 minutes later) and the server
simply shuts itself down (without error messages of any kind). The
SlimServer also fails to start as a service under XP
sporadically/inconsistently after a reboot (I think these two issues are
related).



I have attempted numerous 'fixes' including a 'complete' (does not seem
possible) uninstall and re-install of SlimServer (5.1.5) as well as a failed
attempt to "upgrade" to the latest nightly build.



In the beginning, it seemed to run indefinitely, but I had significant
library/tagging issues that have been described elsewhere in this discussion
list as "[slim]
<http://lists.slimdevices.com/archives/discuss/2004-May/029286.html>
Disappearing/Reattributed Tracks or [slim]
<http://lists.slimdevices.com/archives/discuss/2004-May/029641.html>
Slimserver missing songs and erratic behaviour or [slim]
<http://lists.slimdevices.com/archives/discuss/2004-May/029416.html>
Missing Tracks .. Once I added some new tracks (about 7000 MP3s on a
different physical volume) it seemed to overwhelm the system.



My questions are:

1. Is there an FAQ or "documentation" that describes how best to
organize a collection to optimize performance/stability for the Slim Server?

2. How about the "optimal" use of MP3 tags? Should I use a single
version of tags or multiple? Does it affect rescan performance?
3. Is there a "known" limit on the number of songs that SlimServer can
practically handle?
4. What are the hardware requirements for a 'large' collection?
5. When I reinstall the server, it seems to pick up behaviour from the
previous installation indicating to me that prefs are being stored somewhere
(registry?) How can I eliminate this legacy behaviour?
6. How do I remove the "cookie" or "preference" that brings me to the
same song page every time I connect to the server from a particular machine
on the network?



For the record, my server hardware configuration is:



OS Name Microsoft Windows XP Professional

Version 5.1.2600 Service Pack 1 Build 2600

OS Manufacturer Microsoft Corporation

System Manufacturer VIA Technologies, Inc.

System Model KT600-8237

Processor x86 Family 6 Model 8 Stepping 1 AuthenticAMD ~1760 Mhz

Total Physical Memory 1,024.00 MB

Available Physical Memory 525.82 MB

Total Virtual Memory 2.65 GB

Available Virtual Memory 1.80 GB

Page File Space 1.65 GB



The following is the only record I have of the failure of the service:



[Windows Error Reporting]

5/24/2004 12:31 PM Application Error Faulting application
slim.exe, version 0.0.0.0, faulting module perl58.dll, version 5.8.3.809,
fault address 0x00086920.&#x000d;&#x000a;

5/25/2004 2:43 PM Application Hang Fault bucket
21971969.&#x000d;&#x000a;

5/24/2004 4:44 PM Application Error Fault bucket
99797864.&#x000d;&#x000a;



Thanks in advance for any assistance!!!



Best,



Hugh

Healy
2004-05-25, 15:56
On Tue, 2004-05-25 at 15:02, Hugh Hempel wrote:
> Currently, I can not get SlimServer to run for more than a few hours…
> It appears to me that when the server starts and begins to rescan the
> MP3 library I run out of memory (about 90-120 minutes later) and the
> server simply shuts itself down (without error messages of any kind).
> The SlimServer also fails to start as a service under XP
> sporadically/inconsistently after a reboot (I think these two issues
> are related)…
>

This sounds like the memory leak bug that is in the official 5.1.5
release. I've got about 23,000 tracks and would run out of memory on
the official release. Once I switched to the latest nightly after the
bug was fixed, I've been fine. I run my server on linux so I can't
address your windows specific questions as to why the settings are
hanging around, but I'm sure others on the list will

-Healy