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

Benchmarks #105

Closed
kazimuth opened this issue Aug 11, 2020 · 2 comments
Closed

Benchmarks #105

kazimuth opened this issue Aug 11, 2020 · 2 comments
Labels
A-Build-System Related to build systems or continuous integration C-Performance A change motivated by improving speed, memory usage or compile times

Comments

@kazimuth
Copy link

It would be cool to have some benchmarks for different system components, to make it easier to avoid causing performance regressions. It seems like hecs has some, which is cool.

https://github.com/marketplace/actions/continuous-benchmark could also be fun to set up, it gives you graphs of performance over time like this. Not sure how much time that would add to CI builds though, I haven't used GitHub Actions much. Having a graph that measured average incremental-recompile time could be very helpful in preventing that from creeping up.

@cart
Copy link
Member

cart commented Aug 11, 2020

Thats a fantastic idea. I also really want performance repression tests and would love to seem them in any form.

At the rate that ive been committing, i already capped the free github actions limit back when i had it validate every commit. Now it runs once daily (and for prs) but im still pretty tightly bound. I dont think we could fit perf tests on top. For anything gpu-bound we would need a box with a reasonable gpu, which im guessing we dont get by default.

So i think CI probably isn't feasible until we find funding, but I fully support building up benchmarks to run locally / compare branches. And can always plug those in to CI and cross our fingers 😄

@karroffel karroffel added A-Build-System Related to build systems or continuous integration C-Performance A change motivated by improving speed, memory usage or compile times labels Aug 13, 2020
@alice-i-cecile
Copy link
Member

Work is in progress on this, see #4225. Closing this out now as complete-ish.

maniwani pushed a commit to maniwani/bevy that referenced this issue Jan 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Build-System Related to build systems or continuous integration C-Performance A change motivated by improving speed, memory usage or compile times
Projects
None yet
Development

No branches or pull requests

4 participants