Squeezebox Please queue up several tracks to play on this player and start them playing. Then press the Reset Counters link above to clear the statistics and update this display.
Summary Control Connection : OK Streaming Connection : OK Player Signal Strength : OK Buffer Fullness : OK Server Response Time : OK Warnings This player is performing normally. -------------------------------------------------------------------------------- Player Performance : Squeezebox 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. Player Signal Strength This graph shows the strength of the wireless signal received by your player. Higher signal strength is better. The player reports signal strength while it is playing. < 10 : 0 : 0% < 20 : 0 : 0% < 30 : 0 : 0% < 40 : 0 : 0% < 50 : 0 : 0% < 60 : 0 : 0% < 70 : 0 : 0% < 80 : 482 : 29% ############## < 90 : 1152 : 71% ################################### < 100 : 0 : 0% >=100 : 0 : 0% max : 85.000000 min : 71.000000 avg : 79.796818 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 : 50 : 3% # < 20 : 7 : 0% < 30 : 7 : 0% < 40 : 8 : 1% < 50 : 8 : 1% < 60 : 7 : 0% < 70 : 11 : 1% < 80 : 8 : 1% < 90 : 15 : 1% < 100 : 1324 : 92% ############################################# >=100 : 0 : 0% max : 99.999905 min : 0.000000 avg : 93.901291 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 : 1574 :100% ################################################## < 2 : 0 : 0% < 5 : 0 : 0% < 10 : 0 : 0% < 20 : 0 : 0% >=20 : 0 : 0% max : 0.000000 min : 0.000000 avg : 0.000000 -------------------------------------------------------------------------------- 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 : 13656 : 87% ########################################### < 0.005 : 1765 : 11% ##### < 0.01 : 29 : 0% < 0.015 : 54 : 0% < 0.025 : 72 : 0% < 0.05 : 63 : 0% < 0.1 : 4 : 0% < 0.5 : 9 : 0% < 1 : 0 : 0% < 5 : 0 : 0% >=5 : 0 : 0% max : 0.155321 min : -0.016665 avg : 0.001222 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 : 4300 : 54% ########################### < 0.005 : 663 : 8% #### < 0.01 : 1218 : 15% ####### < 0.015 : 1342 : 17% ######## < 0.025 : 320 : 4% ## < 0.05 : 84 : 1% < 0.1 : 13 : 0% < 0.5 : 2 : 0% < 1 : 0 : 0% < 5 : 0 : 0% >=5 : 0 : 0% max : 0.108551 min : 0.000000 avg : 0.005037 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 : 6358 : 80% ######################################## < 0.005 : 1569 : 20% ######### < 0.01 : 4 : 0% < 0.015 : 1 : 0% < 0.025 : 6 : 0% < 0.05 : 0 : 0% < 0.1 : 4 : 0% < 0.5 : 0 : 0% < 1 : 0 : 0% < 5 : 0 : 0% >=5 : 0 : 0% max : 0.054021 min : -0.015232 avg : 0.001009 It is still stopping half way through a track, and I think my room would be a radiation hazard if I pumped the power up any higher. I'll upgrade to the latest daily build and see if that helps. -- timmorris ------------------------------------------------------------------------ timmorris's Profile: http://forums.slimdevices.com/member.php?userid=4147 View this thread: http://forums.slimdevices.com/showthread.php?t=21947 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
