Background worker throttled to 4 fps on Android?

7 replies
2443 views
Translate

I tried to create an multiplayer game as air app with the AIR 4.0 Beta. It runs the client code in the primary worker and the server logic (when started) on a background worker. But it seems like Adobe hasn't planned for that scenario. Seems that on mobile devices the background worker has a fixed framerate of 4 (profiling with scout told me so). So it is handled like in sleepmode of the app. Thats hard for a running server because the eventphase will be delayed in the worst case by 250 ms. Goodbye good latency. Is there a way to change this behaviour or is a Worker designed to be slow reacting?

This topic is closed to new replies. Start a new post to keep the conversation going.

D

dvdjg

Participant

This is a copy of the text i wrote in the bug base:

After all, Android workers are fine for me.

I solve the problem if the 4fps with a workaround:

I made a loop inside the Background Worker that synchronizes with the main Worker with the help of a Mutex and a Condition. This way the Main does a notifyAll() in its processing frame while the Background Worker stays in the corresponding wait() inside the loop.

Every ~250ms I break the loop, allowing the flow to return to the system and process the Worker messages. It inmediately re-enters the loop and stays there for other ~250ms and so on.

I hope it could be useful fot anyone while waiting for Adobe to fix the bug.

Translate