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

Investigate Examples performance #4066

Open
tybug opened this issue Aug 5, 2024 · 0 comments
Open

Investigate Examples performance #4066

tybug opened this issue Aug 5, 2024 · 0 comments
Labels
performance go faster! use less memory!

Comments

@tybug
Copy link
Member

tybug commented Aug 5, 2024

While investigating #4014, we improved on some performance hits we took during the IR migration (#3921). A remaining holdout is computing _mutator_groups, accounting for 15% of runtime in #4014 (comment), in part composed of _ir_starts_and_ends (7% total runtime).

This seems high to me. We should see if we can track equivalent information inside ConjectureData in a more performant way, for either ir bounds, or mutator groups, or both — or neither, and decide no action is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance go faster! use less memory!
Projects
None yet
Development

No branches or pull requests

1 participant