1 | I'd like to thank the PyTables community that have collaborated in the |
---|
2 | exhaustive testing of Blosc. With an aggregate amount of more than |
---|
3 | 300 TB of different datasets compressed *and* decompressed |
---|
4 | successfully, I can say that Blosc is pretty safe now and ready for |
---|
5 | production purposes. |
---|
6 | |
---|
7 | Other important contributions: |
---|
8 | |
---|
9 | * Valentin Haenel did a terrific work implementing the support for the |
---|
10 | Snappy compression, fixing typos and improving docs and the plotting |
---|
11 | script. |
---|
12 | |
---|
13 | * Thibault North, with ideas from Oscar Villellas, contributed a way |
---|
14 | to call Blosc from different threads in a safe way. Christopher |
---|
15 | Speller introduced contexts so that a global lock is not necessary |
---|
16 | anymore. |
---|
17 | |
---|
18 | * The CMake support was initially contributed by Thibault North, and |
---|
19 | Antonio Valentino and Mark Wiebe made great enhancements to it. |
---|
20 | |
---|
21 | * Christopher Speller also introduced the two new '_ctx' calls to |
---|
22 | avoid the use of the blosc_init() and blosc_destroy(). |
---|
23 | |
---|
24 | * Jack Pappas contributed important portability enhancements, |
---|
25 | specially runtime and cross-platform detection of SSE2/AVX2 as well |
---|
26 | as high precision timers (HPET) for the benchmark program. |
---|
27 | |
---|
28 | * @littlezhou implemented the AVX2 version of shuffle routines. |
---|
29 | |
---|
30 | * Julian Taylor contributed a way to detect AVX2 in runtime and |
---|
31 | calling the appropriate routines only if the undelying hardware |
---|
32 | supports it. |
---|
33 | |
---|
34 | * Kiyo Masui for relicensing his bitshuffle project for allowing the |
---|
35 | inclusion of part of his code in Blosc. |
---|