"kicking" calibre to wake it up required?

[jehrler]

Originally Posted by kovidgoyal

Notifications on macOS happen via separate process asynchronously, so they cant cause pauses. I cant think of anything else that could cause a pause that would affect only the GUI thread and not any other threads. But I agree the issue is likely in the mini, as I suggested before the place to look is the power settings.

As I mentioned in the other thread, the only power setting that wasn't already in non-sleep mode was "put hard disks to sleep when possible". I have turned that off so the disk won't go to sleep. Note that this has not been an issue with other server functionality (vpn,plex).

I also turned off animations in calibre and dock bouncing as a notification method. Calibre would bounce the dock when a wireless connection was made so maybe turning that off will prevent the GUI from interfering with the server connection.

We shall see....

[jehrler]

Issue remains.

[kovidgoyal]

Try hiding calibre (right click on dock icon and select hide).

[jehrler]

I already have it hidden as it is essentially a background process 95% of the time.

[kovidgoyal]

Then I am out of ideas. Since the content server works, I suggest using that directly or using the content server connection in CC.

[chaley]

Originally Posted by kovidgoyal

I cant think of anything else that could cause a pause that would affect only the GUI thread and not any other threads

I don't think it stops only the GUI thread. I think that something the GUI does causes all of calibre to pause.

Originally Posted by kovidgoyal

Since the content server works, I suggest using that directly or using the content server connection in CC.

I suspect that the content server working is accidental, and that it will stop working under some conditions. For example, I think that the following steps will result in a non-responding CS:

1. Start calibre
2. Let the mini go to sleep.
3. Connect CC. Verify that the connection sequence pauses.
4. Connect to the content server using a web browser. I think the connection will hang because the step above has put calibre into some kind of wait state.

Grasping at straws: is there some kind of remote session server running? If so then it could be pausing programs that "output too much" for its buffers.

[jehrler]

Originally Posted by chaley

I don't think it stops only the GUI thread. I think that something the GUI does causes all of calibre to pause.

I suspect that the content server working is accidental, and that it will stop working under some conditions. For example, I think that the following steps will result in a non-responding CS:

1. Start calibre
2. Let the mini go to sleep.
3. Connect CC. Verify that the connection sequence pauses.
4. Connect to the content server using a web browser. I think the connection will hang because the step above has put calibre into some kind of wait state.

Grasping at straws: is there some kind of remote session server running? If so then it could be pausing programs that "output too much" for its buffers.

I believe I've tried this before but will try again and report back here. Just a note that the mini is set to never sleep.

As to your question, as far as I know there are no limits on output...the mini let me start watching a movie using its Plex server even while the calibre wireless connection is stalled.

The remote session client I'm using is using the built in remote login in Mac OS X.

[jehrler]

ok, just confirmed that with the CC wireless connection stalled, connecting to the content server via browser proceeds without issue.

The content server offers up its data both to the iPhone that is still stalled using the CC wireless connection and a separate computer.

Note that accessing the content server, even from the stalled iPhone, has no effect on the wireless connection. It remains stalled.

Just want to point out again that to restart the wireless server does not require logging into the mini. Just having it display a login screen is sufficient.