-
Enhancement
-
Resolution: Fixed
-
P2
-
fx2.0
Currently, pulseRunnable is not posted to the event queue if the previous pulse hasn't yet been processed. That may lead to noticeable periods of idleness from the moment when the current pulse is finished and until a new pulse is scheduled when we run at a rate less that 60 fps in regular mode.
If instead a new pulseRunnable is posted unless there is already a pending pulse event, performance improves. F.e., GUIMark2.Bitmap-3000 benchmark on a local machine improves from 42 fps to 60 fps (hitting the limit, so the actual improvement is even bigger).
If instead a new pulseRunnable is posted unless there is already a pending pulse event, performance improves. F.e., GUIMark2.Bitmap-3000 benchmark on a local machine improves from 42 fps to 60 fps (hitting the limit, so the actual improvement is even bigger).
- blocks
-
JDK-8113170 A simple animation is jerky
- Resolved
-
JDK-8100719 align Pulse to VBlank time to enable smooth, stutter-free animations
- Resolved
-
JDK-8100864 Quantum threading
- Closed
- relates to
-
JDK-8104684 Animation stutters
- Closed
-
JDK-8113170 A simple animation is jerky
- Resolved
-
JDK-8092246 Delays in D3D Present affect performance
- Open
-
JDK-8100622 Allow QuantumRenderer thread and FX Application thread to run in parallel
- Closed
(2 relates to)