------------------------------------------------------------------------
A poll associated with this post was created, to vote and see the
results, please visit http://forums.slimdevices.com/showthread.php?t=32238
------------------------------------------------------------------------
Question: Do you have a intermittent SB GUI pause for 8-30 sec?
    
- Yes, my wireless SB will intermittently pause for 8-30sec.
- Yes my wired SB will intermittently pause for 8-30sec.
- No, my SB GUI does not pause.
------------------------------------------------------------------------

Triode;175884 Wrote: 
> 
> SS drops key presses if they have been queued up for too long.  If you
> edit the perl in Slim/Hardware/IR.pm to change $maxIRQTime you can
> adjust how long is deemed too long.  The idea here is that keeping old
> key presses and processing them too later is worse than loosing them. 
> At present the IR time graph shows how long a key press is stored for,
> but does not show that ones over the threshold above are actually
> droppped without doing anything.
> 
> The server code is single threaded, but tries to maintain audio
> streaming if at all possible.  This is what "Response Time" is really
> recording - the time between checking to see if streaming is needed. 
> However for other functions its possible that UI will be locked out
> because it is single threaded and so a function may take some time and
> the only other thing done when it is running is audio streaming.  So
> when building a web page for example, the player UI will freeze, but
> audio streaming should be maintained.  This is by current design of the
> server.

Well well this is very interesting. Thanks, you are the first person
that's been able to explain this to me so far.

What is the default for maxIRQTime? (I am just starting to look around
SS - and the internal documentation seems, well, limited)

With performance alarms on I am seeing lots of strange 15 second delay
reports that are not showing up in the histograms:

2007-01-30 18:23:39.3165 Select Task      >    .5 : 15.86377   
Slim::Networking::Async::HTTP::_http_read_body
2007-01-30 18:23:39.3330 Timer Late       >    .5 : 15.87504
2007-01-30 18:23:39.3624 Response Time    >    .5 : 15.91006
2007-01-30 18:23:39.3682 Timer Late       >    .5 : 15.69968
2007-01-30 18:23:39.3785 Timer Late       >    .5 : 15.70222
2007-01-30 18:23:39.3904 Timer Late       >    .5 : 15.66950
2007-01-30 18:23:39.4246 Timer Late       >    .5 : 15.69042
2007-01-30 18:23:39.4354 Timer Late       >    .5 : 14.21449
2007-01-30 18:23:39.4426 Timer Late       >    .5 : 13.44166
2007-01-30 18:23:39.4770 Timer Late       >    .5 :  2.34886
2007-01-30 18:23:39.4973 Timer Late       >    .5 :  2.34086
2007-01-30 18:38:39.2370 Select Task      >    .5 : 15.86086   
Slim::Networking::Async::HTTP::_http_read_body
2007-01-30 18:38:39.2536 Timer Late       >    .5 : 15.79570
2007-01-30 18:38:39.2831 Response Time    >    .5 : 15.90738
2007-01-30 18:38:39.2887 Timer Late       >    .5 : 15.56050
2007-01-30 18:38:39.3229 Timer Late       >    .5 : 15.32192
2007-01-30 18:38:39.3576 Timer Late       >    .5 : 15.19713
2007-01-30 18:38:39.4262 Timer Late       >    .5 : 15.20347
2007-01-30 18:38:39.4385 Timer Late       >    .5 : 15.16337
2007-01-30 18:38:39.4493 Timer Late       >    .5 : 14.22114
2007-01-30 18:53:39.3777 Select Task      >    .5 : 15.85946   
Slim::Networking::Async::HTTP::_http_read_body
2007-01-30 18:53:39.3941 Timer Late       >    .5 : 15.65779
2007-01-30 18:53:39.4266 Response Time    >    .5 : 15.90890
2007-01-30 18:53:39.4323 Timer Late       >    .5 : 15.43129
2007-01-30 18:53:39.4760 Timer Late       >    .5 : 15.33866
2007-01-30 18:53:39.5346 Timer Late       >    .5 : 15.25172
2007-01-30 18:53:39.5468 Timer Late       >    .5 : 15.21176
2007-01-30 18:53:39.5577 Timer Late       >    .5 : 15.09981
2007-01-30 18:53:39.5882 Timer Late       >    .5 : 14.35192

I don't think I am using the Web GUI at these times, but I will have to
look more closely.

I have not yet correlated these alarms with UI freeze, but the time
period is darn coincidental.

Is there any way to localize these messages further? How do I figure
out what is setting up or firing the instance of
Slim::Networking::Async::HTTP::_http_read_body?

Now, the really hard part. 

Is there any plan to thread SS? I am willing to put fingers to keyboard
if needed to fix this issue. 

I know many people use the web GUI, but all my devices are far away
from spinning disks and computers, intentionally. So the remote
performance matters tremendously, second only to streaming.


-- 
Eric Carroll

Transporter-Bryston 3B SST-Paradigm Reference Studio 60 v.4
SB3-Rotel RB890-B&W Matrix 805
SB3-Pioneer VSX-49TXi-Mirage OM7+C2+R2
------------------------------------------------------------------------
Eric Carroll's Profile: http://forums.slimdevices.com/member.php?userid=9293
View this thread: http://forums.slimdevices.com/showthread.php?t=32238

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to