RoaringBitmap / RoaringBitmap/CRoaring
Roaring64Map's read,write performance is bad
Open
@Oppen is already working on this.
Since Apr 13, 2022.
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 334
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 17
Description
I found Roaring64Map's read,write method performance is bad. To a bitmap with a cardinality value of 590208, the read method elapsed 120ms, the write method elapsed 100ms. To be more concrete ,the read,write target are all memory ,not disk. The methods are called with the portable parameter be true.
When I have more bitmaps to deserialize to do and,or operations ,then serialize the final bitmap , most of the time will be payed for the deserialization/serialization method.
Any advice will be appreciated. @lemire
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.