weijie

I found the performance reason is due to the map implementation to keep the key,value pair. When deserialized the 64 bit data, we will pay for the cost to insert...

Sorry, I have no time to go on with the C version. I am glad to hear that someone will take on this. I think we will see that soon.

would be glad to do that. But the 64 bit version seems still have evolution space . just hold on this.

shiftLeftFromSpecifiedPosition() is to move the bytes after the removed position to a previouse position one by one. For example: the four bytes of the key is : 8,11, 13, 16...

If the 4 bytes not stored as an int to save the java array object memory footprint,and stored as byte[4] keys, the logic would be as follow : `for (;...

@richardstartin if you still wanna this, would be appreciate you could give a concise description to document this behavior in your native language or pr it.

@richardstartin @lemire I am also interested in this 64 bit bitmap topic. The current Roaring64NavigableMap implementation payed lots of space the TreeMap Integer keys. To my case, I need to...

Thanks for the explanation! @richardstartin @lemire do you have plan to implement the TEB container ? we could cooperate to implement that. Another question about Roaring64NavigableMap why we choose to...

@blacelle I am not sure I got you. What I doubt is that the RoaringArray implementation doest the same thing to keep a key , container pair map by using...

@richardstartin OK. Thanks. So what do you think about the two things : 1st: adding a TEB container. 2nd: the Roaring64NavigableMap could have a jvm better way to store the...