ModelCitizen wrote:
There is a quite a difference between running SlimServer via the remote
as opposed to the web gui. I ran a 192mb, 500ghz PII dedicated Windows
XP machine for Slimserver 5.*/6.2/6.3 for a long while. Using the
remote (my usual device) was fine but the web gui was pretty pants (I
could even say it sucked). Scanning was slow but it always happened
while I was asleep so I didn't care.
Unfortunately 6.5 was too much for this machine so I gave it away.
I'm still on 6.2.2 so perhaps I'll start running into problems when I
upgrade. My current machine has no problems running slimserver. If it
does run into problems I won't be blaming Perl, which is plenty fast in
my experience, but the slimserver coders. The speed of software is
mainly impacted by poor design decisions.
In the case of slimserver I've been wondering about the wisdom of
putting all tasks in one program. Good candidates for running in
seperate modules would probably be the music library indexer (I believe
they actually did that in 6.5) and the web interface. A 'slim' core
slimserver module doing the core business that communicates with the
other modules would seem more logical to me.
I don't mean to imply that the current slimserver is poorly designed. In
fact, I think the programmers did a marvellous job. Also, to butcher a
Dutch expression: The best helmsmen are usually on the shore. ;)
Regards,
Peter
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
