I'm having extramly slow web response from slim server 6.5 on a 2.8 GHz dual core with 1 Gig of ram runing xp sp2 as well. The initial web page takes about 15 seconds to open (even on the server). Other web pages take 5+ seconds for the most part. Painfully slow.
I've enabled server statistics and set the warning threshold to .5. I have not cleaned out the plugins however. I played around n the web interface for a bit and don't notice a difference when I'm streaming and when I'm not but have come up with the following log: Response Time > .5 : 2.66207 Response Time > .5 : 2.65432 Timer Late > .5 : 5.39169 Timer Late > .5 : 5.35924 Timer Late > .5 : 5.29809 Timer Late > .5 : 4.77590 Web Page Build > .5 : 5.64807 Page: playlist.html Select Task > .5 : 5.65810 Slim::Web::HTTP::processHTTP Timer Late > .5 : 1.79268 Web Page Build > .5 : 0.51666 Page: browsedb.html Select Task > .5 : 0.52908 Slim::Web::HTTP::processHTTP Response Time > .5 : 2.63811 Timer Late > .5 : 2.52953 Response Time > .5 : 2.64287 Timer Late > .5 : 4.91616 Timer Late > .5 : 4.93991 Database Access > .5 : 2.51656 DBIx select_single Response Time > .5 : 2.62078 Timer Late > .5 : 7.56193 Timer Late > .5 : 6.90818 Timer Late > .5 : 5.95956 Timer Late > .5 : 5.00998 Web Page Build > .5 : 8.24471 Page: playlist.html Select Task > .5 : 8.25496 Slim::Web::HTTP::processHTTP Timer Late > .5 : 2.79036 Timer Late > .5 : 1.77821 Web Page Build > .5 : 0.59839 Page: browsedb.html Select Task > .5 : 0.61241 Slim::Web::HTTP::processHTTP Web Page Build > .5 : 0.63281 Page: browsedb.html Select Task > .5 : 0.64608 Slim::Web::HTTP::processHTTP Request Task > .5 : 0.56606 Notify: Plugins::RandomPlay::Plugin::commandCallback Response Time > .5 : 0.59826 The first thing I should note is that if one entry is supposed to be present for each slow response, that is not the case. EVERY web page I call for takes 5 seconds or more to display and there aren't nearly as many entries as pages I've opened. Seems to be quite a few late timers - don'tcha think? I don't know the code well enough to understand the relationship of timers with the other items on this list but I suspect there is some interdependency going on here. The other interesting tidbit of data I can provide is that for the most part slim.exe doesn't consume more than 2% of the CPU as indicated by taskman. The only place I see slim.exe spike is when I request it hit the database by browsing music. Then I see a spike of 25-30% CPU usage for one blip on taskman. After that slim goes quiet with a blip of 1-2% for the 5-15 seconds it takes to display the page. If I don't access the database, I don't see the spike in CPU at the web request (setting up statistics, and other non-db related pages). 5-15 second wait times are the norm on this machine, not the exception, so I can gather more data if someone can tell me how to get it. One last note, I don't recall this much pain with the web pages slow response a month or so ago (I could be wrong) so I suspect one of the XP updates might be the culprit (I stay updated). - Ray -- RainmanRam ------------------------------------------------------------------------ RainmanRam's Profile: http://forums.slimdevices.com/member.php?userid=7477 View this thread: http://forums.slimdevices.com/showthread.php?t=30145 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
