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
I've been toying with the idea of making CRoaring benchmarks print their results in a format compatible with the benchstat tool we use in the Go world for comparing different runs. I think it would help us make more informed decisions when optimizing.
Related to this, after we tackle #284 we should be able to use an allocator that keeps track of how many allocations we make and how much memory we use for a given operation, which could further aid comparison.
The text was updated successfully, but these errors were encountered:
I've been toying with the idea of making CRoaring benchmarks print their results in a format compatible with the
benchstat
tool we use in the Go world for comparing different runs. I think it would help us make more informed decisions when optimizing.Related to this, after we tackle #284 we should be able to use an allocator that keeps track of how many allocations we make and how much memory we use for a given operation, which could further aid comparison.
The text was updated successfully, but these errors were encountered: