MinimServer SLOW!

[simoncn]

(06-01-2015 13:11)promao Wrote:  Dear Simon,

Yes, I did did stop the music playing before you changed the logging level back to Info.

I may have a clue: Could this abnormal behavior be consistent to a fault in the wifi network? I have an older Airport Extreme on the living room (where system resides) connecting wirelessly to an Apple Time Capsule on a more distant location. Apparently all devices, iPad included (controlling the DS application of Aries) are in fact only connecting to the distant Time Capsule and not to this Airport Extreme, for some reason.

Could this mean that the delay occurs on the transmission the command on the iPad DS application that only reaches the server with that delay? The delay in seconds on the music was much more than 6 seconds.

Sorry if this may seem a silly question...

Many Thanks.

Pedro

Working backwards, if you stopped the music at 22:15:47.464 and the delay was much more than 6 seconds, it seems there was a long delay between the iPad sending the Play command and Minimserver receiving the HTTP GET request to play the music.

To confirm this, you can repeat the test but modify it slightly, as follows:

1) Browse to a test track that shows the problem but don't play it yet
2) From the minim icon, select 'Show log'
3) In the log window, change the logging level from Info to Debug
4) In the log window, click Clear to clear the log window
5) Leave the log window open

Now play the test track while you are watching the log window. As soon as you select Play, you should see these messages:

Code:

22:15:44.116 Thread-39: HTTPService: accepted incoming connection
22:15:44.116 Thread-39: HTTPService: waiting for incoming connection
22:15:44.117 Thread-38: HTTPService: received request, Socket[addr=/192.168.1.68,port=56211,localport=9790]
22:15:44.117 Thread-38: HTTPService: adding connection org.jminim.lib.HTTPConnection@1752b9e
22:15:44.118 Thread-3614: HTTPConnection: writer thread waiting for request
22:15:44.118 Thread-3615: HTTPConnection: reading HTTP request
22:15:44.119 Thread-3615: GET /minimserver/*/music/John*20Lurie/African*20Swim*20and*20Manny*20*26*20Lo*20-*20Two*20Film*20Scores*20By*20John*20Lurie/01*20Main*20Titles.aif HTTP/1.1
22:15:44.119 Thread-3615: User-Agent: Music Player Daemon 0.18.5, Host: 192.168.1.252:9790, Accept: */*, Icy-Metadata: 1

If there is a long delay before you see these messages, it means the transmission of the Play command is being delayed by the network.