Daniel Lemire
Daniel Lemire
> I already include benchmarks The parseAccessors function is a tiny component of this benchmark.
@spnda Here is my recommendation. Take your current code, do all the parsing and error handling, but do not touch your data structures. Do not call reserve, emplace_back, push_back at...
@spnda The reason I raise these questions is that software performance is complex and requires hard numbers and experimentation. For example, just by tracing the code without too much attention,...
Could other people chime in on this PR?
@AviAvni Would you be interested in proposing a pull request?
@Dr-Emann provided a review. :-)
> about my question about how much memory allocated? Are you asking about what these numbers mean in the 32-bit statistic instances ? ```C++ uint32_t n_bytes_array_containers; /* number of allocated...
> I'm asking if this 3 uint32_t is the overall heap memory allocated for roaring bitmap or there is more memory that allocated that is not on the statistics I...
For example, you might be using copy-on-write and have a seemingly enormous bitmap that uses no memory at all. Then it matters whether you have called `roaring_bitmap_shrink_to_fit` or not. And...
@bearrito Yes. That is a very good first issue. The C code is well tested and should be similar to what is needed in Go: https://github.com/RoaringBitmap/CRoaring/blob/a103d3811702b9389c538881c9974e9a7a7552af/src/roaring.c#L435 It would be highly...