Yehaaaaaah! 6.2 has sorted my problems. I'be been playing with SS for about 2 hours now and am really impressed. Now I can browse all menus perfectly quickly using the remote and all seems to be very, very well indeed. I'd just like to say a huge great thank you to the people who worked to get this going. This really has made my decade.
Just for those who might think that SlimServer needs a large amount of hardware, this is the current spec for my dedicated (and so far very stable) SlimServer laptop: Dell Latitude 500 Mhz P3, 192mb RAM. Windows XP Home SP2 (fresh install) - all extraneous Windows stuff uninstalled or turned off, generally slimmed down as much as possible, disabled all unused hardware and services, only runs SlimServer, priority given to background services, no firewall, no virus checkers, no software, no power saving, defragged before placing in draw and forgetting about it). Total machine RAM usage (Commit Charge) is stable at 113mb. Processor usage during playing hovers between 3% and 6%. However processor usage jumps to 100% when I choose a big menu item (i.e. Genres > Ambient > All albums, which holds 155 flac albums) but does this for less than a second and then the menu displays (i.e pretty instant in my book). All music is flac. Squeezebox2 is currently wired. Library stats: 817 albums with 9086 songs by 1200 artists Music is held in Maxtor OneTouch 300gb USB drive via USB 1. Ha ha. I can't believe how happy I am! At last I can sell the Naim CDX! --------------------------------------------- Triode. I ran Server and Network Health as you asked. Here is the output. It's not perfect but doesn't appear worrying. I wonder how much running the web interface and the annoying refresh on the laptop server influenced the figures (I've just realised that there was also a second instance of the web interface open on my network at the time)? I ran it for about three quarters of an hour. Player Performance : Squeezebox2 The graphs shown here record the long term trend for each of the player performance measurements below. They display the number and percentage of measurements which fall within each measurement band. It is imporant to leave the player playing for a while and then assess the graphs. Buffer Fullness This graph shows the fill of the player's buffer. Higher buffer fullness is better. Note the buffer is only filled while the player is playing tracks. Squeezebox1 uses a small buffer and it is expected to stay full while playing. If this value drops to 0 it will result in audio dropouts. This is likely to be due to network problems. Squeezebox2 uses a large buffer. This drains to 0 at the end of each track and then refills for the next track. You should only be concerned if the buffer fill is not high for the majority of the time a track is playing. Playing remote streams can lead to low buffer fill as the player needs to wait for data from the remote server. This is not a cause for concern. < 10 : 47 : 2% # < 20 : 1 : 0% < 30 : 3 : 0% < 40 : 2 : 0% < 50 : 1 : 0% < 60 : 4 : 0% < 70 : 7 : 0% < 80 : 4 : 0% < 90 : 7 : 0% < 100 : 2151 : 97% ################################################ >=100 : 0 : 0% max : 99.999968 min : 0.000000 avg : 97.271767 Control Connection This graph shows the number of messages queued up to send to the player over the control connection. A measurement is taken every time a new message is sent to the player. Values above 1-2 indicate potential network congestion or that the player has become disconnected. < 1 : 28 :100% ################################################## < 2 : 0 : 0% < 5 : 0 : 0% < 10 : 0 : 0% < 20 : 0 : 0% >=20 : 0 : 0% max : 0.000000 min : -1.000000 avg : -0.035714 -------------------------------------------------------------------------------- Server Performance The graphs shown here record the long term trend for each of the server performance measurements below. They display the number and percentage of measurements which fall within each measurement band. Server Response Time This graph shows the length of time between slimserver responding to requests from any player. It is measured in seconds. Lower numbers are better. If you notice response times of over 1 second this could lead to problems with audio performance. The cause of long response times could be either other programs running on the server or slimserver processing a complex task. < 0.002 : 31298 : 75% ##################################### < 0.005 : 7096 : 17% ######## < 0.01 : 112 : 0% < 0.015 : 2368 : 6% ## < 0.025 : 269 : 1% < 0.05 : 35 : 0% < 0.1 : 248 : 1% < 0.5 : 175 : 0% < 1 : 10 : 0% < 5 : 12 : 0% >=5 : 1 : 0% max : 10.112766 min : -0.008646 avg : 0.004213 Timer Accuracy Slimserver uses a timer mechanism to trigger events such as updating the user interface. This graph shows how accurately each timer task is run relative to the time it was intended to be run. It is measured in seconds. Timer tasks are scheduled by the server to run at some point in the future. As only one timer task can run at once and the server may also be performing other activity, timer tasks always run slightly after the time they are scheduled for. However if timer tasks run significantly after they are scheduled this can become noticable through delay in the user interface. < 0.002 : 1762 : 36% ################# < 0.005 : 1163 : 24% ########### < 0.01 : 1745 : 35% ################# < 0.015 : 110 : 2% # < 0.025 : 32 : 1% < 0.05 : 19 : 0% < 0.1 : 29 : 1% < 0.5 : 44 : 1% < 1 : 5 : 0% < 5 : 18 : 0% >=5 : 2 : 0% max : 14.130860 min : 0.000001 avg : 0.020217 Timer Task Duration This graph shows how long each timer task runs for. It is measured in seconds. If any timer task takes more than 0.5 seconds this is likely to impact the user interface. < 0.002 : 2528 : 51% ######################### < 0.005 : 0 : 0% < 0.01 : 5 : 0% < 0.015 : 2362 : 48% ####################### < 0.025 : 18 : 0% < 0.05 : 3 : 0% < 0.1 : 0 : 0% < 0.5 : 13 : 0% < 1 : 0 : 0% < 5 : 0 : 0% >=5 : 0 : 0% max : 0.296342 min : 0.000193 avg : 0.006775 --------------------------------------------------- Again. THANKS!!!! Whoooooooooooooooo! MC -- ModelCitizen _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
