PDA

View Full Version : Problems with Windows service



Kevin Hawkins
2004-07-28, 10:42
I actually have no problems whatsoever on going out and buying 1GB of RAM if
that is going to fix my problem, a very worthwhile investment. I am not
asking for it to work in 512MB - I just want it to work if I spec the
machine right. I haven't been able to do that so far as the motherboard has
a 512MB limit (CUSL2) . What I am (still) unsure about is whether that is
going to fix the problem. There are conflicting views re this even in these
posts. As I said I believe it's a RAM issue but I'm not certain. Tying this
down would be great. I still worry there are unyielding threads in the code
that cause some issues, particularly around the 15 minute blackouts on
'search for a song', even if the SliMPS displayed 'searching' that would be
a step forward.

From a performance perspective streaming mp3 is not terribly intensive and
when the cpu is driving say 3 slims my cpu usage is running at say 15% so
the glitch seems to be Ram/Paging - Windows which can adequately support
muti channel video streaming surely can't in itself be the culprit here,
hardware resources could. I'll let you know what I find but I do feel the
majority base is Windows and every effort should be made to support the
majority of users. Do Slim Devices actually have any feedback as to which
platform people are running on ? - I would be most interested. Certainly for
the volume market this has to be key.

Kevin

KDF - whilst I may be untypical in terms of the size of this music
collection I am making the effort to retire the 4 CD Sony multichangers I
currently use (200 + 300 + 300 + 300) = over 1000 CD's linked by a Slinke -
so very much an original library here.


> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf
> Of Ben Gladstone
> Sent: 28 July 2004 16:55
> To: Slim Devices Discussion
> Subject: [slim] Problems with Windows service
>
> ditto on the thanks to the slim community for a great &
> free server app
> - and that the windows platform is the key to the mass market
>
> as a sense check on the server hardware, we supply windows
> machines to small businesses and would never spec RAM at
> less than 1GB for a 5-client Exchange server up to 2GB for
> a 15-client server
>
> slimserver is doing a relatively intensive job (it's not just a
> fileserver) so an 8-client server requiring 1GB RAM is
> reasonable - and 1GB of server RAM costs no more than a
> single squeezebox
>
>
> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf
> Of Jeff Allison
> Sent: 28 July 2004 16:23
> To: 'Slim Devices Discussion'
> Subject: [slim] Problems with Windows service
>
> > > Moving the box to Linux isn't an option for me - but would
> > > installing Perl on Windows and running the Slim
> software through
> > > that make any difference?
>
> > not likely, as the EXE is simply a perl compile under a
> windows Perl
> > environment. I too see the same lame performance under
> windows. no
> > dropouts, but I only have 4k songs under windows ( I
> keep legal, you
> > see). Testing options just isn't an option becuase once
> again, you
> > have to pay money to play with windows. That's probably
> why nobody
> > can help. Windows users can only cry for help. I can't
> develop a
> > damn thing for any windows app I've tried and i
> certainly know of a
> > great many that need a big injection of user feedback.
> for myself, I
> > can only say that I try. I do have a duplicate setup. I
> do have an
> > entire drive dedicated to a windows slimserver setup,
> even tho I would
> > never run my clients from it. It is just there to test
> my ideas,
> > hoping it can work in windows as wel as it does on my
> main slimserver
> > platform. or at least, to avoid breaking things.
>
> I believe that KDF has supplied a bunch of stuff to the
> slim community including, I think, the nice fishbone skin
> that I use all the time. For that, and for all the
> volunteer efforts going on, many thanks! It's great that
> people will do this. Also, this is a discussion list and
> not the official slim devices tech support forum, so
> everyone is free to voice their opinions and one should
> not expect a response to every post to this list.
>
> But saying that windows sucks isn't a very useful
> response. I'm not personally a big fan of windows myself,
> but for various reasons it's what I run at home and it's
> what the slim server is running on. I've been having some
> problems that originated this thread -- although I don't
> actually think the problems that I'm seeing are the same
> as what is being discussed now. I don't have "performance
> problems" per se, I have about once a day occurrences
> where the client cannot connect to the server -- and Dean
> is looking into my problems. He has suggested some things
> I can do to track down information and we're working the issue.
> I can't ask for any more than that at present. But
> getting back to windows, it has to be Slim Devices'
> priority. You can't sell a consumer electronics device
> that requires a Linux server on the back end, so you have
> to support windows. And even with the tech-savvy,
> geek-ish crowd that owns slim devices products I'd guess
> that a significant majority are running the server on windows.
>
> - Jeff
>
>
> > -kdf
> >
>
____________
> Discuss mailing list
> Discuss (AT) lists (DOT) slimdevices.com
> http://lists.slimdevices.com/lists/listinfo/discuss
>

kdf
2004-07-28, 11:04
Quoting Kevin Hawkins <lists (AT) ukusa (DOT) demon.co.uk>:

> I actually have no problems whatsoever on going out and buying 1GB of RAM if
> that is going to fix my problem, a very worthwhile investment. I am not
> asking for it to work in 512MB - I just want it to work if I spec the
> machine right. I haven't been able to do that so far as the motherboard has
> a 512MB limit (CUSL2) . What I am (still) unsure about is whether that is
> going to fix the problem. There are conflicting views re this even in these
> posts. As I said I believe it's a RAM issue but I'm not certain. Tying this
> down would be great. I still worry there are unyielding threads in the code
> that cause some issues, particularly around the 15 minute blackouts on
> 'search for a song', even if the SliMPS displayed 'searching' that would be
> a step forward.

The unfortunate thing with any system is that there are so many variables in the
hardware, it is nearly impossible to measure for sure what gains you will get
from any given change. One way to perhaps test the theory before you go and
spend the money is to reduce your library temporarily. You dont even have to
move the files, just point the server to some place deeper in your library
folders. Try 50,000 files, 25,000. post the results. post them to
bugs.slimdevices.com along with a request for a page on the website with user
configuration data. Best way to have your problem fixed is take part in its
solution. Then, if they dont respond to being handed the information, I'll
join you in kicking butt :)

For the record, when I do run slimserver on windows its an old Athlon 700MHz
Slot1 cpu, 256M ram and about 5000 songs. The response is noticeably slower
but I do not experience dropouts. With this system, I wouldn't want to rely on
it handling two synced players while transcoding.


> >From a performance perspective streaming mp3 is not terribly intensive and
> when the cpu is driving say 3 slims my cpu usage is running at say 15% so
> the glitch seems to be Ram/Paging - Windows which can adequately support
> muti channel video streaming surely can't in itself be the culprit here,
> hardware resources could. I'll let you know what I find but I do feel the
> majority base is Windows and every effort should be made to support the
> majority of users. Do Slim Devices actually have any feedback as to which
> platform people are running on ? - I would be most interested. Certainly for
> the volume market this has to be key.

I believe Dean has posted numbers based on the downloads in this forum before.
Windows, as I recall is the majority. However the fundamental goal is
multi-platform. Windows, whether by design or by accident of history, doesn't
play well with others. That doesn't mean it sucks, just that it has different
requirements. Perl allows the same code to run on many different systems,
which means you benefit from faster development and less waisting time having
to port every fix or change. The downside is that in order to run in windows,
it needs an added layer, and added resources.

>
> KDF - whilst I may be untypical in terms of the size of this music
> collection I am making the effort to retire the 4 CD Sony multichangers I
> currently use (200 + 300 + 300 + 300) = over 1000 CD's linked by a Slinke -
> so very much an original library here.

sounds like a good goal.