PDA

View Full Version : More On 5.1.XX Woes



Kenneth Watt
2004-05-17, 15:49
> Aha, 100,000 tracks? What are the specs of the machine? (How much
> memory, CPU?)
> Can you bring up the Task Manager and look at the CPU usage and Memory
> usage and let me know what you see?
> That's a fairly large library, I want to make sure that if there is a
> bug we fix it.

Okay, I realise that it's a pretty big library and therefore I am in a kinda
unique position to an extent.

The machine should more than cope with it, it's a 2Ghz P4 with half a meg of
RAM on a decent Gigabyte mobo using Maxtor drives almost exclusively, I
think there may be a rouge 120Gb IBM pile of cr*p there as well but there's
nothing on that. It is running under a fully patched Win XP SP1 release.

Using 5.1.1 it's bugged out a couple of times tonight already whilst playing
back with it reading a memory usage of >300,000K at it's peak that I saw
down to just over 200,000K and it keeps on locking up. The player display
either locks or just blanks. CPU usage was normally sitting in excess of 90%
all the time whilst scanning, drops to 0 when it locks. Sometimes it will
drop to sensible levels, but not often.

Trying to start the Slim Server on the host PC it just seems to sit on the
start up screen for ages doing not a lot, but the service is alive.

Much the same happened with later versions, but the lock-ups were worse, far
worse. Also as the server ran the slower the PC would respond until it
became totally unresponsive. So far on 5.1.1 that hasn't happened but bear
in mind it takes a fair while to scan that many tracks. ;)

> Ok. If you have time, I'd love for you to try out the latest nightly
> and help us figure out what the problem is so we can fix it.

Hopefully all the above helps a bit.

K.

kdf
2004-05-17, 16:10
A major difference between 5.1.1 and 5.1.5 is that the server needs to rescan
eveyr single time you restart in 5.1.1. The overhead of the scan is less, but
you have to keep redoing it. The latest nightly takes care of a lot of the
rescanning problems so that you can start playback as soon as possible after any
restart. The problem is, with 100,000 tracks, you may have to wait a very long
time for a full scan after wiping the cache. This wait could be painfully long,
depending on your file system and drive usage. I would try leaving it to scan
overnight. Once you have a complete scan, it should be much more responsive. My
windows setup only has 5000 tracks for testing and I tend to walk away and get a
snack if I wipe the cache. however, startup time after a full scan is under a
minute.

As there is every intention of making a new official release soon, it will help
a great deal to have every bit of input possible on the current nightly builds.
This way, 5.2 can really be the latest and greatest. I do testing on both Linux
and Windows, using iTunes, Moodlogic and raw scans, but I dont have access to
100,000 songs, or the time to try every possible feature under all conditions.
There are several others on this list who ride the crest of the wave, but having
one of the largest libraries I have know about makes your input very useful.

-kdf

Quoting Kenneth Watt <kwatt (AT) funkycool (DOT) co.uk>:

> > Aha, 100,000 tracks? What are the specs of the machine? (How much
> > memory, CPU?)
> > Can you bring up the Task Manager and look at the CPU usage and Memory
> > usage and let me know what you see?
> > That's a fairly large library, I want to make sure that if there is a
> > bug we fix it.
>
> Okay, I realise that it's a pretty big library and therefore I am in a kinda
> unique position to an extent.
>
> The machine should more than cope with it, it's a 2Ghz P4 with half a meg of
> RAM on a decent Gigabyte mobo using Maxtor drives almost exclusively, I
> think there may be a rouge 120Gb IBM pile of cr*p there as well but there's
> nothing on that. It is running under a fully patched Win XP SP1 release.
>
> Using 5.1.1 it's bugged out a couple of times tonight already whilst playing
> back with it reading a memory usage of >300,000K at it's peak that I saw
> down to just over 200,000K and it keeps on locking up. The player display
> either locks or just blanks. CPU usage was normally sitting in excess of 90%
> all the time whilst scanning, drops to 0 when it locks. Sometimes it will
> drop to sensible levels, but not often.
>
> Trying to start the Slim Server on the host PC it just seems to sit on the
> start up screen for ages doing not a lot, but the service is alive.
>
> Much the same happened with later versions, but the lock-ups were worse, far
> worse. Also as the server ran the slower the PC would respond until it
> became totally unresponsive. So far on 5.1.1 that hasn't happened but bear
> in mind it takes a fair while to scan that many tracks. ;)
>
> > Ok. If you have time, I'd love for you to try out the latest nightly
> > and help us figure out what the problem is so we can fix it.
>
> Hopefully all the above helps a bit.
>
> K.
>
>
>