-
Notifications
You must be signed in to change notification settings - Fork 283
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
Holding space for memory benchmarking issues #5967
Comments
This was referenced May 21, 2024
If we feel we might benefit from repetitions, we could try writing our own benchmark class - ASV is designed for this and they are not as complex as I feared.
|
This was referenced May 23, 2024
This was referenced Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since #5960, #5959 , #5950 and especially #5948
We are likely to get a few change warnings from memory benchmarks.
Doubtless some sensitivity changes may be needed, perhaps we'll have to turn off most of the memory benchmarking again. But possibly also, it will need to "settle down" after recent changes ?
I think we should just routinely close these for a while, and later review as a set.
Issues referencing this one will be visible below ...
The text was updated successfully, but these errors were encountered: