It is important to track animation performance through our performance benchmarks. However it's also interesting to know the performance of real-world applications. The problem is that this typically requires instrumenting the apps, which can be difficult, is sometimes disagreeable, and at times not even feasible (3rd party apps for which we don't have source).
Before Preview we had such a mechanism, but it had two problems that interfered with running applications: it was activated by a user gesture (control-alt-click) that was always active and could conflict with application code, and it displayed FPS on top of the application itself. This lead to RT-254, and the feature was disabled for Preview.
Similar functionality should be restored, however it should be activated via the standard JDK Logging mechanism, and should provide data via a Logger, rather than by interfering with the running of the app itself.
Before Preview we had such a mechanism, but it had two problems that interfered with running applications: it was activated by a user gesture (control-alt-click) that was always active and could conflict with application code, and it displayed FPS on top of the application itself. This lead to RT-254, and the feature was disabled for Preview.
Similar functionality should be restored, however it should be activated via the standard JDK Logging mechanism, and should provide data via a Logger, rather than by interfering with the running of the app itself.
- relates to
-
JDK-8107870 General FPS reporting (RT-997) broken in Marina b11
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
JDK-8090961 Mechanism to report FPS of an arbitrary app (app doesn't call PerformanceTracker) in Prism
-
- Open
-
-
-
- Closed
-