roaring
roaring copied to clipboard
What's the largest golang bitmap size used in production?
would like to know
- size and size of the bitmap in exported bytes
- performance of the bitmap with statistics / benchmark
- use case scenario , preferably for golang.
does anyone hv these info?
I have individual bitmaps that are probably in the order of tens or hundreds of millions of values; I also use a huge number of them, but sizes are likely to vary a lot between them. I could write a short program to give you an approximate number on Monday. Those created with roaring
, consumed by gocroaring
to convert them to frozen format (I'll migrate to roaring
after the frozen support is released :) ) and then consumed by a thin Cython wrapper around croaring
. The frozen ones are actually bigger because they are the union of many of the former ones.
As for what's the use, I probably need to ask permission to my manager to disclose. I don't think it's business critical, so I'll most likely get a "yes", but you know, skipping the formalities can bring him and I problems.
For performance I have some very simplistic numbers from a profiling session trying to optimize the middle step, but 1) I'm not sure if those are the numbers we're looking for, 2) it's currently for the gocroaring
version and 3) I'd need to ask for permission for that too.
EDIT: I'll have my 1:1 with the manager on Monday. I'll try to remember to ask for clearance on this.
More than 500M members in a single set, takes less than 300MiB when stored. On my dev machine manages to consume >4M CheckedAdd()s per second. That's what I can tell.