Open Supermath101 opened 2 years ago
Per Discord, this still happens on the old renderer, and on 0.5, correct?
For reference: I'm getting about 1-2% CPU usage with a very basic scene on the same commit.
Per Discord, this still happens on the old renderer, and on 0.5, correct?
Correct.
I’m wondering if somehow vsync is turned off.
Yup this is almost certainly due to a lack of frame limiting. Right now vsync is our only default form of frame limiting, which isn't great for a variety of reasons:
On top of that, we'll need to sort out a new way to handle "delta times" anyway when we enable "actual parallel pipelining" in the new renderer, which im still working on. I might just add "on by default" frame limiting with those changes, as I think the changes I need to make have lots of overlap with frame limiting.
@TheRawMeatball and I discussed frame-rate limiting before (inspired by the user who hit the change detection warning overnight). Seems like it'd be a small change to the winit loop. Relevant discussion. https://discord.com/channels/691052431525675048/743663924229963868/906440570203942972
Bevy version
Commit ID:
e8412df0
Operating system & version
Manjaro Linux with Nvidia proprietary drivers.
What you did
I ran a very basic Pipelined rendering app on release mode.
What you expected to happen
This example code should in-theory run at near 0% CPU utilization.
What actually happened
The CPU utilization was hovering around 1/3 usage.
Additional information
The output of running
cargo-flamegraph
: flamegraph.zipI'm running an Intel Core i7-9750H with 16 GB of RAM.
This was the 2nd item that was logged (I thought it might be useful):