I started a thread in the 3rd Party Plugins forum, about use of the web
front end taking so many resources that (AlienBBC) streaming music
freezes ("AlienBBC - radio stations interrupted by web page access")

After some suggestions I upgraded from 6.22 to the lastest 6.5 Beta, in
the hope that the combination of MySQL and split-scanner might sort out
my problems. This has certainly helped, and the freeezes are now less
often. 

I still get such problems though, and I assume these are down to lack
of communication between the server & client. After a suggestion on the
other thread I set --perfwarn=0.5.

I now get lots of log output, as just about anything web related seems
to talke longer than half a second (even when nothing is happening).

To give some an extreme examples, here are the sort of things logged
when I slect "All Songs" on the web page:


Code:
--------------------
    
  2006-07-02 17:40:25.0129 Timer Late > 0.5 : 2.54691505432129
  2006-07-02 17:42:04.1963 Web Page Build > 0.5 : 204.450978040695
  2006-07-02 17:42:04.2009   Generating page for browsedb.html
  2006-07-02 17:42:04.2676 Select Task > 0.5 : 204.671139955521
  2006-07-02 17:42:04.2857   Slim::Web::HTTP::processHTTP
  2006-07-02 17:42:04.2884 IR Delay > 0.5 : 198.674467802048
  2006-07-02 17:42:05.1504 Web Page Build > 0.5 : 0.698230028152466
  2006-07-02 17:42:05.1545   Generating page for status_header.html
  2006-07-02 17:42:05.1607 Select Task > 0.5 : 0.866274118423462
  2006-07-02 17:42:05.1633   Slim::Web::HTTP::processHTTP
  2006-07-02 17:42:05.9030 Select Task > 0.5 : 0.580109119415283
  2006-07-02 17:42:05.9057   Slim::Web::HTTP::processHTTP
  2006-07-02 17:42:05.9081 IR Delay > 0.5 : 0.678067922592163
  2006-07-02 17:42:05.9293 IR Delay > 0.5 : 0.698479890823364
  2006-07-02 17:42:05.9415 IR Delay > 0.5 : 0.709849119186401
  2006-07-02 17:42:05.9535 IR Delay > 0.5 : 0.721158981323242
  2006-07-02 17:42:05.9682 IR Delay > 0.5 : 0.733943939208984
  2006-07-02 17:42:05.9820 IR Delay > 0.5 : 0.747066020965576
  2006-07-02 17:42:36.1573 Select Task > 0.5 : 0.735414981842041
  
--------------------



204 seems a lot of seconds to wait for a web page to come back. Also,
during that time the squeezebox is completely unresponsive.
During this time slimserver.pl averages around 92% CPU, with flac,
mplayer, mysql fighting for the rest.


It has been suggested to me that this might be best discussed in the
Beta forum, so here I am.


My set-up:

I am running the very latest (at time of typing) SlimServer build -
6.5b1 - 8242.

My OS is Linux Fedora FC5 with no X-Windows or unneccessary services. 
I run this on an Epia Via motherboard with a 1Ghz processor and 512MB
RAM. No other software (other than directly related to SlimServer) runs
on this machine.

I have one client - a Squeezebox 3. I nornally run this wirelessly, but
when I tried it wired I didn't see any obvious impreovement.

My music library contains 535 albums with 6451 songs by 232 artists.



I hoped that 512MB of RAM (with very little used by the OS) would allow
for the database to do some really good caching (especially given the
relatively small amount of music I have), thus giving quick web access.
Is there anything I can do to force the database to use spare memory for
cache? Any other suggestions gratefuly received...

Cheers,

Richard


-- 
SadGamerGeek
------------------------------------------------------------------------
SadGamerGeek's Profile: http://forums.slimdevices.com/member.php?userid=6145
View this thread: http://forums.slimdevices.com/showthread.php?t=25173

_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta

Reply via email to