You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Criterion has some issues around handling of our allocation count/size benchmarks.
Values of 0 are never accepted, even for a custom measurement type. Unfortunately, we often desire having zero allocations!
The values produced by these benchmarks are causing NaN propagation somewhere within criterion. This directly prevents plotting of results as well as saving estimates/tukey values for our allocation benchmarks.
We should take some time to work on the upstream library to improve these pain points.
The text was updated successfully, but these errors were encountered:
FelixMcFelix
changed the title
Benchmarks::
Benchmarks: plots not saved or compared for alloc_sz/_ct benchmarks
Mar 8, 2024
Criterion has some issues around handling of our allocation count/size benchmarks.
0
are never accepted, even for a custom measurement type. Unfortunately, we often desire having zero allocations!We should take some time to work on the upstream library to improve these pain points.
The text was updated successfully, but these errors were encountered: