C-Blosc2: A simple, compressed, fast and persistent data store library for C¶
The Blosc Development Team
- Code of Conduct
What is it?¶
Blosc is a high performance compressor optimized for binary data (i.e. floating point numbers, integers and booleans). It has been designed to transmit data to the processor cache faster than the traditional, non-compressed, direct memory fetch approach via a memcpy() OS call. Blosc main goal is not just to reduce the size of large datasets on-disk or in-memory, but also to accelerate memory-bound computations.
C-Blosc2 is the new major version of C-Blosc, with full support for 64-bit containers, filter pipelining, new filters, new codecs, dictionaries for improved compression ratio and much more (see our ROADMAP for an updated list of features). The new 64-bit data containers support both sparse and contiguous storage, either in-memory or on-disk. The contiguous frame is a very simple format , meant to be used for either persistency or for sending to other processes or machines. The sparse frame is a simple extension of the contiguous format that allows for storing chunks individually in a local filesystem (using key/value stores in the future is planned). Finally, the frames can be annotated with metainfo (metalayers, variable-length metalayers) that is provided by the user. More info about the improved capabilities of C-Blosc2 can be found in this talk.
C-Blosc2 tries hard to be backward compatible with both the C-Blosc1 API and its in-memory format. Furthermore, if you just use the C-Blosc1 API, you are guaranteed to generate compressed data containers that can be read with C-Blosc2, but getting the benefit of better performance, like for example leveraging the accelerated versions of codecs present in Intel’s IPP (like LZ4).
C-Blosc2 is currently in release candidate stage, so not ready to be used in production yet. Having said this, the release candidate stage means that the API has been declared frozen, so there is guarantee that your programs will continue to work with future versions of the library. If you want to collaborate in this development you are welcome. We need help in the different areas listed at the ROADMAP; also, be sure to read our DEVELOPING-GUIDE and our Code of Conduct. Blosc is distributed using the BSD license.
Meta-compression and other advantages over existing compressors¶
C-Blosc2 is not like other compressors: it should rather be called a meta-compressor. This is so because it can use different codecs (libraries that can reduce the size of inputs) and filters (libraries that generally improve compression ratio). At the same time, it can also be called a compressor because it makes an actual use of the several codecs and filters, so it can actually work like so.
Currently C-Blosc2 comes with support of BloscLZ, a compressor heavily based on FastLZ, LZ4 and LZ4HC, Zstd, and Zlib, via zlib-ng:, as well as a highly optimized (it can use SSE2, AVX2, NEON or ALTIVEC instructions, if available) shuffle and bitshuffle filters (for info on how shuffling works, see slide 17 of http://www.slideshare.net/PyData/blosc-py-data-2014).
Blosc is in charge of coordinating the codecs and filters so that they can leverage the blocking technique (described above) as
well as multi-threaded execution (if several cores are available) automatically. That makes that every codec and filter
will work at very high speeds, even if it was not initially designed for doing blocking or multi-threading. For example,
Blosc allows you to use the
LZ4 codec, but in a multi-threaded way.
Another important aspect of C-Blosc2 is that it splits large datasets in smaller containers called chunks, which are basically Blosc1 containers. For maximum performance, these chunks are meant to fit in the LLC (Last Level Cache) of CPUs. In practice this means that in order to leverage C-Blosc2 containers effectively, the user should ask for C-Blosc2 to uncompress the chunks, consume them before they hit main memory and then proceed with the new chunk (as in any streaming operation). We call this process Streamed Compressed Computing and it effectively avoids uncompressed data to travel to RAM, saving precious time in modern architectures where RAM access is very expensive compared with CPU speeds.
As said, C-Blosc2 adds a powerful mechanism for adding different metalayers on top of its containers. Caterva is a sibling library that adds such a metalayer specifying not only the dimensionality of a dataset, but also the dimensionality of the chunks inside the dataset. In addition, Caterva adds machinery for retrieving arbitrary multi-dimensional slices (aka hyper-slices) out of the multi-dimensional containers in the most efficient way. Hence, Caterva brings the convenience of multi-dimensional containers to your application very easily. For more info, check out the Caterva documentation.
Compiling the C-Blosc2 library with CMake¶
Blosc can be built, tested and installed using CMake. The following procedure describes a typical CMake build.
Create the build directory inside the sources and move into it:
$ cd c-blosc2-sources $ mkdir build $ cd build
Now run CMake configuration and optionally specify the installation directory (e.g. ‘/usr’ or ‘/usr/local’):
$ cmake -DCMAKE_INSTALL_PREFIX=your_install_prefix_directory ..
CMake allows to configure Blosc in many different ways, like prefering internal or external sources for compressors or enabling/disabling them. Please note that configuration can also be performed using UI tools provided by CMake (ccmake or cmake-gui):
$ ccmake .. # run a curses-based interface $ cmake-gui .. # run a graphical interface
Build, test and install Blosc:
$ cmake --build . $ ctest $ cmake --build . --target install
The static and dynamic version of the Blosc library, together with header files, will be installed into the specified CMAKE_INSTALL_PREFIX.
Once you have compiled your Blosc library, you can easily link your apps with it as shown in the examples/ directory.
Handling support for codecs (LZ4, LZ4HC, Zstd, Zlib)¶
C-Blosc2 comes with full sources for LZ4, LZ4HC, Zstd, and Zlib and in general, you should not worry about not having (or CMake not finding) the libraries in your system because by default the included sources will be automatically compiled and included in the C-Blosc2 library. This means that you can be confident in having a complete support for all the codecs in all the Blosc deployments (unless you are explicitly excluding support for some of them).
If you want to force Blosc to use external libraries instead of the included compression sources:
$ cmake -DPREFER_EXTERNAL_LZ4=ON ..
You can also disable support for some compression libraries:
$ cmake -DDEACTIVATE_ZSTD=ON ..
C-Blosc2 is meant to support all platforms where a C99 compliant C compiler can be found. The ones that are mostly tested are Intel (Linux, Mac OSX and Windows), ARM (Linux, Mac), and PowerPC (Linux) but exotic ones as IBM Blue Gene Q embedded “A2” processor are reported to work too. More on ARM support in README_ARM.rst.
For Windows, you will need at least VS2015 or higher on x86 and x64 targets (i.e. ARM is not supported on Windows).
For Mac OSX, make sure that you have installed the command line developer tools. You can always install them with:
$ xcode-select --install
For Mac OSX on arm64 architecture, you need to compile like this:
$ CC="clang -arch arm64" cmake ..
Support for the LZ4 optimized version in Intel IPP¶
C-Blosc2 comes with support for a highly optimized version of the LZ4 codec present in Intel IPP, and actually if the cmake machinery in C-Blosc2 discovers IPP installed in your system it will use it automatically by default. Here it is a way to easily install Intel IPP in Ubuntu machines:
$ wget https://apt.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS-2019.PUB $ apt-key add GPG-PUB-KEY-INTEL-SW-PRODUCTS-2019.PUB $ sudo sh -c 'echo deb https://apt.repos.intel.com/ipp all main > /etc/apt/sources.list.d/intel-ipp.list' $ sudo apt-get update && sudo apt-get install intel-ipp-64bit-2019.X # replace .X by the latest version
Check Intel IPP website for instructions on how to install it for other platforms.
Display error messages¶
By default error messages are disabled. To display them, you just need to activate the Blosc tracing machinery by setting
BLOSC_TRACE environment variable.
There is an official mailing list for Blosc at: