And, newly available, here's the output of the perfmon display, having reset counters at start of track 2. Note I deleted the summary and some explanatory text.
Player Performance : Office_Softsqueeze Buffer Fullness < 10 : 62 : 33% ################ < 20 : 2 : 1% < 30 : 1 : 1% < 40 : 1 : 1% < 50 : 2 : 1% < 60 : 1 : 1% < 70 : 2 : 1% < 80 : 28 : 15% ####### < 90 : 42 : 23% ########### < 100 : 45 : 24% ############ >=100 : 0 : 0% max : 99.931717 min : -300.000000 avg : 3.117672 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 : 4 :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 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 : 3528 : 83% ######################################### < 0.005 : 565 : 13% ###### < 0.01 : 153 : 4% # < 0.015 : 4 : 0% < 0.025 : 10 : 0% < 0.05 : 9 : 0% < 0.1 : 3 : 0% < 0.5 : 1 : 0% < 1 : 0 : 0% < 5 : 0 : 0% >=5 : 0 : 0% max : 0.196408 min : 0.000032 avg : 0.001350 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 : 1374 : 91% ############################################# < 0.005 : 32 : 2% # < 0.01 : 63 : 4% ## < 0.015 : 39 : 3% # < 0.025 : 1 : 0% < 0.05 : 2 : 0% < 0.1 : 1 : 0% < 0.5 : 0 : 0% < 1 : 0 : 0% < 5 : 0 : 0% >=5 : 0 : 0% max : 0.085037 min : 0.000000 avg : 0.001172 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 : 1510 :100% ################################################# < 0.005 : 0 : 0% < 0.01 : 0 : 0% < 0.015 : 0 : 0% < 0.025 : 0 : 0% < 0.05 : 0 : 0% < 0.1 : 1 : 0% < 0.5 : 1 : 0% < 1 : 0 : 0% < 5 : 0 : 0% >=5 : 0 : 0% max : 0.102007 min : 0.000043 avg : 0.000620 -- mkosma _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
