PDA

View Full Version : Sudden poor performance with wired SB3



twynne
2006-08-29, 11:43
Thought I'd post this here before I start randomly trying different things in an attempt to improve the situation, but one of my SB3's (strangely enough, the wired rather than the wireless) has started stuttering and failing to respond to the remote. An identical SB3 (wired, but connected via a wireless bridge in another room) works fine. This suggests to me that the issue is unlikely to be the server.

I'm running server v6.2.2, and both players report firmware v48. The wired player is connected directly to my router (Vigor 2600VG), as is the server machine (Windows 2003 Server). There is a router firmware available, but it's only a minor update and I'm loathe to mess with router firmware except as a last resort.

Does anyone have a similar setup and/or a suggestion as to where to start? I hadn't upgraded slimserver as some of the reports in the forum didn't look so positive (regarding v6.3), but do you think this would help? I've copied the performance stats below in case this helps (apologies for the long post!). Interesting BTW that it reports my SB3 as an SB2... not sure if this is just an incorrect description somewhere or it actually thinks it's a SB2?!

Thanks all,

Tom

Lounge


Summary
Control Connection : OK
Streaming Connection : OK
Player Signal Strength : OK
Buffer Fullness : Low
Server Response Time : Occasional Poor Response

Warnings
The playback buffer for this player is occasionally falling lower than ideal. This is a Squeezebox2 and so the buffer fullness is expected to drop at the end of each track. You may see this warning if you are playing lots of short tracks. If you are hearing audio dropouts, please check our network signal strength.

Your server response time is occasionally longer than desired. This may cause audio dropouts, especially on Slimp3 and Squeezebox1 players. It may be due to background load on your server or a slimserver task taking longer than normal.


--------------------------------------------------------------------------------

Player Performance : Lounge
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 : 346 :100% ##################################################
< 20 : 0 : 0%
< 30 : 0 : 0%
< 40 : 0 : 0%
< 50 : 0 : 0%
< 60 : 0 : 0%
< 70 : 0 : 0%
< 80 : 0 : 0%
< 90 : 0 : 0%
< 100 : 0 : 0%
>=100 : 0 : 0%
max : 8.241463
min : 0.000000
avg : 0.320798
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 : 95 :100% ##################################################
< 2 : 0 : 0%
< 5 : 0 : 0%
< 10 : 0 : 0%
< 20 : 0 : 0%
>=20 : 0 : 0%
max : 0.000000
min : -1.000000
avg : -0.105263

--------------------------------------------------------------------------------

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 : 2650 : 81% ########################################
< 0.005 : 254 : 8% ###
< 0.01 : 126 : 4% #
< 0.015 : 31 : 1%
< 0.025 : 65 : 2%
< 0.05 : 88 : 3% #
< 0.1 : 33 : 1%
< 0.5 : 22 : 1%
< 1 : 0 : 0%
< 5 : 6 : 0%
>=5 : 4 : 0%
max : 12.765302
min : 0.000050
avg : 0.019958
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 : 1179 : 81% ########################################
< 0.005 : 128 : 9% ####
< 0.01 : 39 : 3% #
< 0.015 : 52 : 4% #
< 0.025 : 3 : 0%
< 0.05 : 2 : 0%
< 0.1 : 5 : 0%
< 0.5 : 7 : 0%
< 1 : 5 : 0%
< 5 : 14 : 1%
>=5 : 13 : 1%
max : 12.245010
min : 0.000000
avg : 0.107779
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 : 1219 : 84% ##########################################
< 0.005 : 220 : 15% #######
< 0.01 : 2 : 0%
< 0.015 : 0 : 0%
< 0.025 : 0 : 0%
< 0.05 : 0 : 0%
< 0.1 : 1 : 0%
< 0.5 : 5 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.117811
min : 0.000057
avg : 0.001062

Mark Lanctot
2006-08-29, 16:00
There were a few Squeezebox firmware updates that specifically addressed problems with the Draytek routers, although this was wireless.

The router firmware update would be best, although again the fixes are for wireless. Still, it seems like your router is choking.

cliveb
2006-08-30, 03:46
Thought I'd post this here before I start randomly trying different things in an attempt to improve the situation, but one of my SB3's (strangely enough, the wired rather than the wireless) has started stuttering and failing to respond to the remote. An identical SB3 (wired, but connected via a wireless bridge in another room) works fine. This suggests to me that the issue is unlikely to be the server.
If it's only just started happening, when all worked OK before, could it be that your external IP address is being enthusiastically probed, and the router is having to spend a lot of time dealing with the "packet storm" and updating its logs? I have no idea how much of a router's resources could be tied up in repelling invaders, so I could be way off base here. But it might be worth checking the router logs to see if there has been a lot of blocked traffic from the Internet.