CRoaring | Roaring bitmaps in C with SIMD ( AVX2
kandi X-RAY | CRoaring Summary
kandi X-RAY | CRoaring Summary
CRoaring is a C library. CRoaring has no bugs, it has no vulnerabilities and it has medium support. However CRoaring has a Non-SPDX License. You can download it from GitHub.
Bitsets, also called bitmaps, are commonly used as fast data structures. Unfortunately, they can use too much memory. To compensate, we often use compressed bitmaps. Roaring bitmaps are compressed bitmaps which tend to outperform conventional compressed bitmaps such as WAH, EWAH or Concise. They are used by several major systems such as Apache Lucene and derivative systems such as Solr and Elasticsearch, Metamarkets' Druid, LinkedIn Pinot, Netflix Atlas, Apache Spark, OpenSearchServer, Cloud Torrent, Whoosh, InfluxDB, Pilosa, Bleve, Microsoft Visual Studio Team Services (VSTS), and eBay's Apache Kylin. The CRoaring library is used in several systems such as Apache Doris. The YouTube SQL Engine, Google Procella, uses Roaring bitmaps for indexing.
Bitsets, also called bitmaps, are commonly used as fast data structures. Unfortunately, they can use too much memory. To compensate, we often use compressed bitmaps. Roaring bitmaps are compressed bitmaps which tend to outperform conventional compressed bitmaps such as WAH, EWAH or Concise. They are used by several major systems such as Apache Lucene and derivative systems such as Solr and Elasticsearch, Metamarkets' Druid, LinkedIn Pinot, Netflix Atlas, Apache Spark, OpenSearchServer, Cloud Torrent, Whoosh, InfluxDB, Pilosa, Bleve, Microsoft Visual Studio Team Services (VSTS), and eBay's Apache Kylin. The CRoaring library is used in several systems such as Apache Doris. The YouTube SQL Engine, Google Procella, uses Roaring bitmaps for indexing.
Support
Quality
Security
License
Reuse
Support
CRoaring has a medium active ecosystem.
It has 1271 star(s) with 225 fork(s). There are 52 watchers for this library.
There were 5 major release(s) in the last 12 months.
There are 44 open issues and 180 have been closed. On average issues are closed in 60 days. There are 1 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of CRoaring is v1.3.0
Quality
CRoaring has 0 bugs and 0 code smells.
Security
CRoaring has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
CRoaring code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
CRoaring has a Non-SPDX License.
Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.
Reuse
CRoaring releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
It has 97 lines of code, 3 functions and 1 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of CRoaring
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of CRoaring
CRoaring Key Features
No Key Features are available at this moment for CRoaring.
CRoaring Examples and Code Snippets
No Code Snippets are available at this moment for CRoaring.
Community Discussions
No Community Discussions are available at this moment for CRoaring.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install CRoaring
The CRoaring library can be amalgamated into a single source file that makes it easier for integration into other projects. Moreover, by making it possible to compile all the critical code into one compilation unit, it can improve the performance. For the rationale, please see the SQLite documentation, https://www.sqlite.org/amalgamation.html, or the corresponding Wikipedia entry (https://en.wikipedia.org/wiki/Single_Compilation_Unit). Users who choose this route, do not need to rely on CRoaring's build system (based on CMake). We maintain pre-generated amalgamated files at https://github.com/lemire/CRoaringUnityBuild for your convenience. To generate the amalgamated files yourself, you can invoke a bash script... (Bash shells are standard under Linux and macOS. Bash shells are available under Windows as part of the GitHub Desktop under the name Git Shell. So if you have cloned the CRoaring GitHub repository from within the GitHub Desktop, you can right-click on CRoaring, select Git Shell and then enter the above commands.). It is not necessary to invoke the script in the CRoaring directory. You can invoke it from any directory where you want the amalgamation files to be written. It will generate three files for C users: roaring.h, roaring.c and amalgamation_demo.c... as well as some brief instructions. The amalgamation_demo.c file is a short example, whereas roaring.h and roaring.c are "amalgamated" files (including all source and header files for the project). This means that you can simply copy the files roaring.h and roaring.c into your project and be ready to go! No need to produce a library! See the amalgamation_demo.c file.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page