Thanks. The 'problem' I am trying to address is to get the web interface to work more quickly. I primarily use the web interface, not the remote. It can take 30 seconds to load certain pages (like Browse Albums or Browse Artists). The music library is about 10K songs. The slow load times are not related to the network as best I can tell - it is a wired network and the slow load times occur both from client machines and on the machine running slimserver. I have also shut down musicmagic to see if that helps. Not appreciably.
Memory usage - Musicmagic uses about 24 MB and slim.exe is using about 70 MB. I lowered the database cache size to 130000.
I really don't think it is much of a RAM problem: I notice that the CPU pretty much gets maxed out when loading pages like Browse Artists, Browse Albums. It just may be that I need to move slimserver to a machine with a faster CPU. I was hoping I could use the older PIII as it is a perfectly fine machine.
Any other suggestions would be great.
On 1/31/06, radish <[EMAIL PROTECTED]> wrote:
Well, firstly you don't state what you're trying to achieve - is there a
specific problem you're trying to solve?
To answer some of your points in a general sense:
> I set it to optimize for background services,
> rather than applications under Performance Options (I assume this
> should
> help as slimserver does run as a system service and that is also the
> way
> musicmagic is setup). I don't see any difference however.
>
Doesn't surprise me. What that setting does is prioritize background
processes over foreground ones. You don't really have any foreground
ones, so it won't make much difference.
>
> a. Keep Unswapped Interval - the default is 30. Should I lower this, to
> say
> 10 or 5? Will it make a difference?
>
Unlikely to make much difference. Windows is unlikely to swap out
slimserver unless it has to (i.e. it's short of ram) - you have a
decent amount and again, nothing else running, so it's unlikely to be
swapped out. If anything turning that feature off may prevent
occasional "hangups" of the interface.
>
> b. Database Temporary File - Set to Use RAM. I am sure this is best
>
Yup.
>
> c. DB Cache Size Tuning - the default is 10,000. I increased this
> 170,000,
> under the assumption that this would use roughly 250 MB RAM, using the
> guideline that 10000 uses about 15 MB. Is this too much, or too
> little? Any advice?
>
Use as much as you can get away with, but maybe not quite that much.
With 512 available, I'd be wary of going much above 200 for the process
as a whole - what does music magic use?
--
radish
------------------------------------------------------------------------
radish's Profile: http://forums.slimdevices.com/member.php?userid=77
View this thread: http://forums.slimdevices.com/showthread.php?t=20641
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
