RoaringBitmap / RoaringBitmap/RoaringFormatSpec
[question] any suggestion about compressing serialized data?
Nobody has claimed this yet.
- Dominant language
- Kaitai Struct
- Stars
- 191
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
suppose i have multiple clients implemented in different languages(go, java...), and all of them need to download roaringbitmap from server through http.
when bitmap gets large(about 10 millions) and serialized binary data comes out about 20 MB, i think compress before sending may save a lot of transmission time.
i am trying use gzip. any suggestions about compressing?
thanks in advance
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.
Research direction
No repository file, test, or entry point is named. Review the Roaring bitmap serialization and HTTP transport assumptions, then compare gzip with the interoperability needs of the Go and Java clients. Done means documenting a concrete compression recommendation and any format or transport constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- networking, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100