BMessageRunner granularity is too high

[joeyadams]

While porting a game of mine to Haiku, I reached a point where I needed a periodic timer to update the game state at roughly 60 frames per second. The closest things I could find to this in the API were Pulse() and BMessageRunner. Though these do send messages periodically, they have a granularity limit of around 10 intervals per second. I then looked in the Media kit and BTimeSource, and was confused quite quickly. Lastly, I asked on the mailing list how to do what I want, and the solution I arrived at was to implement it manually using threads, semaphores, and callbacks.

Other GUI toolkits I've seen have Timers which can be set to periodically send messages at arbitrary rates. I believe the Haiku API should also have this feature, most likely in the form of a BTimer.

To this end, I have attached a working draft and example for a BTimer system. It provides a convenient interface for scheduling messages and callbacks to run at periodic intervals. It would be nice to see it included in the Haiku API, most likely in the Support kit. However, it would need to be reviewed by more experienced eyes.

[joeyadams]

First draft implementation of a BTimer API

[eml]

I'm not a dev, but I had a quick look at the patch anyways. Seems to me that the implementation does what it should do, however I think you should review the coding guidelines: ​Haiku Coding Guidelines

Some examples of 'violations' include member variable names and that a functions return type should be on its own line before the actual declaration. Generally header files use the extension '.h', not '.hpp'. I would suggest putting the public interface first in your class definition as that is the general way it's done throughout the Haiku source code from what I gather. Even though this is a first draft as you say, I would suggest that you write your functions in source files and not in header files.

[stippi]

In the current form, the patch provides these adventages over BMessageRunner:

• Finer granularity,
• With the callback version, one does not need a BHandler/BLooper as the target for the timer events.

Recently, we've been discussing a possibility how the first problem could be fixed for BMessageRunner while significantly reducing the overhead (no extra thread). Not introducing another API is of course more elegant. It would not offer the callback feature, but perhaps this one is tricky anyway, since the callback is called in the timer thread. Application developers may not be expecting this, since it's not what happens in other frameworks like Qt or Gtk.

As for the code of the patch, it indeed does not follow the coding style, but it also has too little error checking for my taste. For example the indication of the running of the timer and quitting of the thread is error prone. Instead of checking the running variable, it could instead check an error from acquiring the semaphore. Then the master thread could destroy the semaphore and then also wait for the timer thread to exit, which is another problem of the patch. I also think the BTimerList should be internal.

[nielx]

Obsoleted patch because of reviews. See comment:2 and comment:5.

Feel free to attach an updated version.

[X512]

Benchmark result for BMessageRunner, X: delay, Y: error, units: seconds

[X512]

Benchmark result for snooze_until, single thread.

[X512]

Scatter plot,red: BMessageRunner, blue: snooze_until (single thread)

[X512]

I attached results of some tests when ​https://review.haiku-os.org/c/haiku/+/2888 is applied.

[axeld]

Thanks! Have you looked into how these numbers change if there are more users of the API? As a simple test one could just run multiple instances of those tests at the same time, also both of them.

Besides this, I'm too dumb to read the exponential notation ;-)

[X512]

X: requested delay, Y: difference between requested and actual delay. Red: 8 test threads, blue: 1 thread.

[tqh]

The granularity has now been reduced a lot in hrev57498, so considering this fixed.