3 ms·
Not in my book. I am running a prototype immediate mode gui that I built for my yet unreleased engine and the frame time is staying below 500ns for a fullscree
by stephc_int13 6y ago
Not in my book.
I am running a prototype immediate mode gui that I built for my yet unreleased engine and the frame time is staying below 500ns for a fullscreen app with many widgets and layers.
The whole thing is built on C + Vulkan but is not entirely optimized yet.
And this is running on a decent but not extremely fast computer. (An Intel NUC from 2018)
- cycloptic 6y agoNow take that same code and run it on a mobile device. Can you say for certain that it's making optimal use of power? And if not, what changes would you have to make so it does?
- stephc_int13 6y agoI'll do that later but I don't think it will lead to extreme CPU consumption. There are many ways to improve performances of idle/almost idle ui. Caching can be useful for large blocks of text as it tend to be the slowest thing to render. But it is preferable to incrementally optimize/add complexity and check assumptions and not make large architectural decisions ahead of time. One way to reason about it is to think in terms of pure data transformations.
- cycloptic 6y agoIf you're caching data, you now have stored state and it's no longer a pure data transformation. You will run into these performance problems with any large data set, not just blocks of text.
- adamnemecek 6y agoCan I see a screenshot?
- stephc_int13 6y agoI plan to publish several articles about my engine later this year, but I am not ready to show it yet.