yaniki

I just discovered, that on my mac, when I switch off (set to "0") "displaylink" attr rendering performance is dramatically increasing (especially if I'm using [jit.gl.multiple] object). It's about 30% faster with "displaylink 0".

This is, of course, not a problem - I'm very happy with that... but why it works this way?

displaylink-attribute-of-the-jit-world-and-jitter-rendering-performance

what i've found in investigating various user reports and my own observations, is that on 10.10 +, enabling displaylink will favor GUI updates and other CPU tasks over rendering. so if you have displaylink enabled, and your patch causes GUI updates to happen, or utilizes the CPU (e.g matrix or physics processing) at framerate, then your jit.world FPS will suffer. also, if your patch is not able to perform at the display rate interval (e.g. 60FPS for most displays), then displaylink also seems to cause worse performance.

It's very interesting and highly useful. Actually, you opened my eyes on some important things I didn't considered before.

Is this the equivalent of toggling the @sync attribute of jit.gl.render?

On my computers "sync" attribute doesn't interfere with the performance. Only "displaylink" behave this way.

the sync attribute modifies a property of the gl context, telling it to only swap buffers on display refresh.

displaylink tells jit.world to trigger drawing based on a callback from the OS (which also happens to be triggered by the display refresh).

in theory, if your display is 60hz, and your patch is able to run at 60fps, then you should leave sync and displaylink enabled for the most stable performance. if your patch is unable to keep up with display refresh rate, then you should disable both attributes, and set your fps to be 1/2 of the display rate.

the sync attribute modifies a property of the gl context, telling it to only swap buffers on display refresh. 

displaylink tells jit.world to trigger drawing based on a callback from the OS (which also happens to be triggered by the display refresh).
conceptually, they're pretty similar.

in theory, if your display is 60hz, and your patch is able to run at 60fps, then you should leave sync and displaylink enabled for the most stable performance. if your patch is unable to keep up with display refresh rate, then you should disable both attributes, and set your fps to be 1/2 of the display rate.


I think, asking about "displaylink" was like opening the Pandora's box...

"displaylink" attribute of the [jit.world] and jitter rendering performance