Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP benchmarking and testing for renderers #1492

Closed
wants to merge 1 commit into from

Conversation

ids1024
Copy link
Contributor

@ids1024 ids1024 commented Oct 26, 2022

This shows iced_glow outperforming iced_wgpu. Probably not accurate, some something may be wrong in the rendering and timing here? It should also test with more primitivies.

Tests pass when combined with #1485 and #1491.

@ids1024
Copy link
Contributor Author

ids1024 commented Oct 26, 2022

I wanted benchmarking of some kind to answer questions about how the glow and wgpu backends compare in performance, whether or not the texture atlas performs better than separate textures or a texture array, etc. Though the numbers don't entirely make sense currently so more work here is probably needed.

But similar logic helps to automatically test that rendering produces the expected output. Might be good to get that working on CI if possible (should be possible to use both glow and wgpu with software rendering?).

This shows `iced_glow` outperforming `iced_wgpu`. Probably not accurate,
something may be wrong in the rendering and timing here? It should also
test with more primitivies.

Tests pass when combined with iced-rs#1485
and iced-rs#1491.
@bungoboingo
Copy link
Contributor

There has been some discussion regarding CI rendering performance measurements to detect potential regressions using offscreen rendering. I have a branch where I started some work on integrating tracy & chrome tracing support for perfetto which would be super beneficial I think! At least I don't know of a faster profiler than tracy. Am looking at Bevy heavily for inspiration here, they have great profiling tools.

@ids1024
Copy link
Contributor Author

ids1024 commented Oct 27, 2022

Good point about Bevy. It makes sense that this is something they have worked on too.

@hecrj
Copy link
Member

hecrj commented Apr 12, 2023

This is cool! Thank you.

I think we can come back to it when we start focusing on optimization.

@hecrj hecrj closed this Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants