smaz
Snappy
Our great sponsors
smaz | Snappy | |
---|---|---|
3 | 5 | |
1,131 | 5,987 | |
- | 0.8% | |
0.0 | 2.6 | |
over 4 years ago | 8 days ago | |
C | C++ | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
smaz
-
Advanced MessagePack capabilities
Choose the data compression algorithm based on the specifics of your data. For example, if you are working with lots of short strings, take a look at [*SMAZ](https://github.com/antirez/smaz).*
-
Improving short string compression.
Take a look at this. Idea behind it seems nice, but it's fixed dictionary ("codebook") was clearly made for English language, and the algorithm itself is really simple. How can we impove on this? Dynamic dictionary won't do, since you have to store it somewhere, nullifying benefits of using such algorithm. Beyond that I have no idea.
-
C Deep
smaz - Efficient string compression library. BSD-3-Clause
Snappy
-
Why I enjoy using the Nim programming language at Reddit.
Another example of Nim being really fast is the supersnappy library. This library benchmarks faster than Google’s C or C++ Snappy implementation.
-
Stretch iPhone to Its Limit: 2GiB Stable Diffusion Model Runs Locally on Device
It doesn't destroy performance for the simple reason that nowadays memory access has higher latency than pure compute. If you need to use compute to produce some data to be stored in memory, your overall throughput could very well be faster than without compression.
There have been a large amount of innovation on fast compression in recent years. Traditional compression tools like gzip or xz are geared towards higher compression ratio, but memory compression tends to favor speed. Check out those algorithms:
* lz4: https://lz4.github.io/lz4/
* Google's snappy: https://github.com/google/snappy
* Facebook's zstd in fast mode: http://facebook.github.io/zstd/#benchmarks
-
Compression with best ratio and fast decompression
Google released Snappy, which is extremely fast and robust (both at compression and decompression), but it's definitely not nearly as good (in terms of compression ratio). Google mostly uses it for real-time compression, for example of network messages - not for long-term storage.
-
How to store item info?
Just compress it! Of course if you will you ZIP, players will able to just open this zip file and change whatever they want. But you can use less popular compression algorithms which are not supported by default Windows File Explorer. Snappy for example.
- What's the best way to compress strings?
What are some alternatives?
LZMAT - git mirror of LZMAT (http://www.matcode.com/lzmat.htm)
zstd - Zstandard - Fast real-time compression algorithm
doboz
LZ4 - Extremely Fast Compression algorithm
brotli - Brotli compression format
ZLib - A massively spiffy yet delicately unobtrusive compression library.
LZHAM - Lossless data compression codec with LZMA-like ratios but 1.5x-8x faster decompression speed, C/C++
LZMA - (Unofficial) Git mirror of LZMA SDK releases
Minizip-ng - Fork of the popular zip manipulation library found in the zlib distribution.
zlib-ng - zlib replacement with optimizations for "next generation" systems.