> Kevin Hawkins
> Sent: 28 January 2004 17:13
> To: 'Slim Devices Discussion'
> Subject: [slim] Brought SliMP3 server down
>
> Restarted WinXP - Slim service has restarted OK - initial
> 5MB RAM allocation (80%cpu) grows to 128MB presumably
> after reading the database and then drops to 10% cpu usage
> - but still no display on Slimp3's and no web access.
An update - after leaving the apparently dead server running for
over 10 minutes with no displays on the SliMP3's I see it has now taken to
servicing the clients. Now this is a 2.66Ghz machine with 1GB RAM and no
other processes running. It strikes me that the display routines - and I
would guess - alongside that any streaming routines are just being starved
during this time. I feel this creates a poor user experience - is there no
way of improving this at all ?
This is a powerful machine albeit with a very large library - which
the server is now rebuilding (!). So the database cache doesn't avoid a
rescan on boot , or faciltate a rapid initial usage of the server on boot -
what does it do ?? Or maybe the Windows bit doesn't work right yet ?
Certainly the database is being built (and updated) as I can see the file
changing.
Kevin
> Sent: 28 January 2004 17:13
> To: 'Slim Devices Discussion'
> Subject: [slim] Brought SliMP3 server down
>
> Restarted WinXP - Slim service has restarted OK - initial
> 5MB RAM allocation (80%cpu) grows to 128MB presumably
> after reading the database and then drops to 10% cpu usage
> - but still no display on Slimp3's and no web access.
An update - after leaving the apparently dead server running for
over 10 minutes with no displays on the SliMP3's I see it has now taken to
servicing the clients. Now this is a 2.66Ghz machine with 1GB RAM and no
other processes running. It strikes me that the display routines - and I
would guess - alongside that any streaming routines are just being starved
during this time. I feel this creates a poor user experience - is there no
way of improving this at all ?
This is a powerful machine albeit with a very large library - which
the server is now rebuilding (!). So the database cache doesn't avoid a
rescan on boot , or faciltate a rapid initial usage of the server on boot -
what does it do ?? Or maybe the Windows bit doesn't work right yet ?
Certainly the database is being built (and updated) as I can see the file
changing.
Kevin