PDA

View Full Version : Slooow remote response



pkfox
2006-12-18, 06:32
I am experiencing very slow remote control response times on my SB3 ( to the extent it is virtually unusable ), I have SS running on a ReadyNas NV ( has been for quite some time without a problem ) the SS version is 6.5.1 - 10479 - Linux, this has only started in the last couple of weeks and I can't think what could have changed, I've done the usual thing of rebooting everything but all to no avail, any help appreciated as I'm on the verge of reverting to my CD player, thanks, BTW I also put new batteries in the remote

Mark Lanctot
2006-12-18, 07:17
Go to Help - Server & Network Health - Enable Performance Monitoring, play a few tracks and post the output.

pkfox
2006-12-18, 08:53
Hello Mark, is this what you need ?, the player actually works ok (apart from dropouts with internet radio now and again )
thanks

The server is currently collecting performance statistics for this player.

You may set warning thresholds for each measurement. This will record in the server log whenever the threshold is exceeded. The most recent log entries can be viewed here.
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 : 2 : 40% ####################
< 90 : 2 : 40% ####################
< 100 : 1 : 20% ##########
>=100 : 0 : 0%
max : 90.000000
min : 75.000000
avg : 82.400000

Warning Thresholds : Low High
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/3 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 : 0 : 0%
< 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 : 5 :100% ##################################################
>=100 : 0 : 0%
max : 99.999682
min : 99.879487
avg : 99.960976

Warning Thresholds : Low High
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 : 0 : 0%
< 2 : 0 : 0%
< 5 : 0 : 0%
< 10 : 0 : 0%
< 20 : 0 : 0%
>=20 : 0 : 0%
max : 0.000000
min : 0.000000
avg : 0.000000

Warning Thresholds : Low High
Warning Thresholds : Low High

pkfox
2006-12-18, 08:56
Go to Help - Server & Network Health - Enable Performance Monitoring, play a few tracks and post the output.

just to update you I notice this piece of info has changed

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 : 29 :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

Mark Lanctot
2006-12-18, 08:57
Whoops, sorry, I should have specified to enable Performance Monitoring then post the output from Server Statistics.

All this is telling us is that your player is good, which is good, but that likely isn't the problem anyway. You probably have poor server response.

Mark Lanctot
2006-12-18, 08:58
just to update you I notice this piece of info has changed

These statistics will change continuously as you play.

pkfox
2006-12-18, 09:12
Thanks Mark here it is


Slim Devices
Server Statistics
Home / Server & Network Health / Server Statistics

The server is currently collecting performance statistics for various internal server functions. These graphs are intended to be used to help diagnose performance issues with the server and its plugins.

You may set warning thresholds for each measurement. This will record in the server log whenever the threshold is exceeded. The most recent log entries can be viewed here.
Server Response Time
The response time of the server - the time between successive calls to select.

< 0.002 : 2619 : 10% #####
< 0.005 : 12929 : 52% #########################
< 0.01 : 3862 : 15% #######
< 0.015 : 1164 : 5% ##
< 0.025 : 973 : 4% #
< 0.05 : 724 : 3% #
< 0.1 : 1889 : 8% ###
< 0.5 : 885 : 4% #
< 1 : 11 : 0%
< 5 : 1 : 0%
>=5 : 1 : 0%
max : 17.269178
min : 0.001283
avg : 0.016798

Warning Thresholds : Low High Backtrace
Timer Lateness
The time between when a timer task was scheduled and when it is run.

< 0.002 : 233 : 8% ####
< 0.005 : 193 : 7% ###
< 0.01 : 1730 : 62% ###############################
< 0.015 : 104 : 4% #
< 0.025 : 55 : 2%
< 0.05 : 87 : 3% #
< 0.1 : 141 : 5% ##
< 0.5 : 211 : 8% ###
< 1 : 18 : 1%
< 5 : 0 : 0%
>=5 : 5 : 0%
max : 321.776873
min : 0.000000
avg : 0.579683

Warning Thresholds : Low High Backtrace
Select Task Duration
The length of time taken by each task run by select.

< 0.002 : 494 : 7% ###
< 0.005 : 135 : 2% #
< 0.01 : 4518 : 67% #################################
< 0.015 : 1322 : 20% #########
< 0.025 : 52 : 1%
< 0.05 : 20 : 0%
< 0.1 : 21 : 0%
< 0.5 : 66 : 1%
< 1 : 16 : 0%
< 5 : 68 : 1%
>=5 : 2 : 0%
max : 5.044589
min : 0.000601
avg : 0.041479

Warning Thresholds : Low High Backtrace
Timer Task Duration
The length of time taken by each timer task.

< 0.002 : 20 : 1%
< 0.005 : 362 : 13% ######
< 0.01 : 1169 : 42% #####################
< 0.015 : 4 : 0%
< 0.025 : 4 : 0%
< 0.05 : 978 : 35% #################
< 0.1 : 225 : 8% ####
< 0.5 : 14 : 1%
< 1 : 1 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.724188
min : 0.001903
avg : 0.025015

Warning Thresholds : Low High Backtrace
Execute / Notification Task Duration
The length of time taken by each execute command or notification callback.

< 0.002 : 25 : 12% #####
< 0.005 : 18 : 9% ####
< 0.01 : 83 : 40% ###################
< 0.015 : 18 : 9% ####
< 0.025 : 10 : 5% ##
< 0.05 : 19 : 9% ####
< 0.1 : 6 : 3% #
< 0.5 : 26 : 12% ######
< 1 : 3 : 1%
< 5 : 2 : 1%
>=5 : 0 : 0%
max : 1.224710
min : 0.000521
avg : 0.057323

Warning Thresholds : Low High Backtrace
Scheduler Task Duration
The length of time taken by each scheduled task.

< 0.002 : 0 : 0%
< 0.005 : 0 : 0%
< 0.01 : 0 : 0%
< 0.015 : 0 : 0%
< 0.025 : 0 : 0%
< 0.05 : 0 : 0%
< 0.1 : 0 : 0%
< 0.5 : 0 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.000000
min : 0.000000
avg : 0.000000

Warning Thresholds : Low High Backtrace
Database Access
The time taken for information to be retrieved from the database.

< 0.002 : 1212 : 78% #######################################
< 0.005 : 0 : 0%
< 0.01 : 1 : 0%
< 0.015 : 1 : 0%
< 0.025 : 14 : 1%
< 0.05 : 298 : 19% #########
< 0.1 : 17 : 1%
< 0.5 : 3 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.157796
min : 0.001063
avg : 0.008128

Warning Thresholds : Low High Backtrace
Web Page Build
The length of time taken to build each web page.

< 0.002 : 0 : 0%
< 0.005 : 0 : 0%
< 0.01 : 0 : 0%
< 0.015 : 0 : 0%
< 0.025 : 0 : 0%
< 0.05 : 0 : 0%
< 0.1 : 0 : 0%
< 0.5 : 7 : 8% ###
< 1 : 35 : 38% ###################
< 5 : 50 : 54% ###########################
>=5 : 0 : 0%
max : 4.926012
min : 0.180260
avg : 2.225583

Warning Thresholds : Low High Backtrace
Process Template
The time to process each Template Toolkit template when building web pages.

< 0.002 : 240 : 2%
< 0.005 : 6777 : 47% #######################
< 0.01 : 4385 : 30% ###############
< 0.015 : 507 : 4% #
< 0.025 : 176 : 1%
< 0.05 : 32 : 0%
< 0.1 : 528 : 4% #
< 0.5 : 1733 : 12% #####
< 1 : 32 : 0%
< 5 : 44 : 0%
>=5 : 0 : 0%
max : 4.131523
min : 0.001824
avg : 0.040837

Warning Thresholds : Low High Backtrace
IR Queue Length
The delay between an IR key press being received and being processed.

< 0.002 : 0 : 0%
< 0.005 : 12 : 30% ###############
< 0.01 : 4 : 10% #####
< 0.015 : 0 : 0%
< 0.025 : 0 : 0%
< 0.05 : 2 : 5% ##
< 0.1 : 7 : 18% ########
< 0.5 : 11 : 28% #############
< 1 : 1 : 2% #
< 5 : 3 : 8% ###
>=5 : 0 : 0%
max : 1.162659
min : 0.003006
avg : 0.192678

Warning Thresholds : Low High Backtrace
Warning Thresholds : Low High

Mark Lanctot
2006-12-18, 09:24
This is telling us one thing we know already - that IR response time is slow. 8% of IR commands take between 1 and 5 seconds and 2% of IR commands take between 0.5 and 1 seconds. This is a very long time for IR commands.

28% of IR commands take between 0.1 and 0.5 seconds to process. This is also quite slow for IR response.

This is also telling us something we don't know and that you haven't commented on: web page response is very slow as well - 54% of web page builds take between 1 and 5 seconds.

All in all, it's indicating the server is having a hard time keeping up, probably due to a lack of resources, most likely memory.

As to where to go from here, it's hard to say. Try to minimize the load on the server: don't use the web UI unless you need it, and try to minimize the plugins you're using. Is your ReadyNAS being used for other tasks (i.e. bittorrent?) Try to move ReadyNAS tasks like bittorrent and ftp to a PC if you can.

Hopefully others will have other suggestions. You may want to check the 3rd Party Hardware forum.

pkfox
2006-12-18, 10:05
thanks Mark , I was thinking along these lines, not a lot I can do with the NAS as I almost exclusively use it for SS, at least I know now thanks again

Triode
2006-12-18, 13:02
Web page build will be slow on a NAS. Is the IR response better if you don't use the web interface?

Try putting 0.5 in the High warning threshold box at the bottom of the server statistics page and pressing set all. Then post what log.txt shows after a while. This should tell us what is taking a long time. However if the NAS does not have enough memory, it won't be able to measure delays due to swapping. How much memory do you have?

pkfox
2006-12-19, 03:17
Web page build will be slow on a NAS. Is the IR response better if you don't use the web interface?

Try putting 0.5 in the High warning threshold box at the bottom of the server statistics page and pressing set all. Then post what log.txt shows after a while. This should tell us what is taking a long time. However if the NAS does not have enough memory, it won't be able to measure delays due to swapping. How much memory do you have?

Hi there, I don't usually use the Web interface I only used it to enable performance statistics as requested by another poster, I've disabled all other services on the NAS ftp,cifs etc..., the NAS has 256mb of RAM, the strange thing is this behaviour has only started very recently - could it be the firmware upgrade on the NAS which now has SS embedded as opposed to an add-on ? thanks, will try your suggestion (0.5) when I am at home