Replies: 2 comments 3 replies
-
Bump, bump, still a giant difference of 90ms native vs 12ms on https://egui.rs on the latest 0.31.0 |
Beta Was this translation helpful? Give feedback.
2 replies
-
You can use puffin to see where the time is being spent on your game vs on the demo app. Just copy this to your code and use puffin_viewer to see the data: egui/crates/egui_demo_app/src/main.rs Lines 62 to 80 in 510b3cd |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there, community! I am currently integrating
egui
to mywgpu
game using the official examples, via theegui-wgpu
andegui-winit
crates. Running theegui_demo_lib
application with all the subwindows open takes ~120ms (--release
, most of the time is taken by running the application itself, so I assume layouting and such), compared to the browser number of ~13ms.Why such a performance difference? Have I skipped something? Here is the renderer implementation I have stripped from the official examples:
I really, really want to use
egui
for the UI in the game, but current performance I am getting is not feasible, unfortunately.Some additional info:
egui_demo_lib
itselfegui_demo_lib
in the same waywinit
In advance, great thanks for the help!
Beta Was this translation helpful? Give feedback.
All reactions