Snappy
jsony
| Snappy | jsony | |
|---|---|---|
| 5 | 4 | |
| 5,994 | 254 | |
| 0.6% | - | |
| 5.2 | 5.2 | |
| 17 days ago | 10 days ago | |
| C++ | Nim | |
| GNU General Public License v3.0 or later | MIT License |
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.
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?
jsony
-
Nim v2.0 Released
Nim's default json library is terrible in performance, but there're much faster drop-in replacements like jsony[1]. I'm not sure that's the main issue for low rank, but it's definitely one of them.
1. https://github.com/treeform/jsony
-
Why I enjoy using the Nim programming language at Reddit.
One of the fastest things I have written in Nim is a JSON parsing library. Why is it fast? Well, it uses Nim’s metaprogramming to parse JSON directly into typed objects without any intermediate representations or any unnecessary memory allocations. This means I can skip parsing JSON into a dictionary representation and then converting from the dictionaries to the real typed objects.
- Setup a Website with Nim
-
Nim vs Python: json serialization performance
The nim stdlib's json(due to how it works) is relatively slow. Jsony Jason are some alternatives that are more performant and speeeedy.
What are some alternatives?
zstd - Zstandard - Fast real-time compression algorithm
supersnappy - Dependency-free and performant Nim Snappy implementation.
LZ4 - Extremely Fast Compression algorithm
glfm - Wrapper of GLFM (OpenGL ES and input for iOS and Android) library for Nim.
brotli - Brotli compression format
fungus - Object variants done like other langugaes
ZLib - A massively spiffy yet delicately unobtrusive compression library.
npeg - PEGs for Nim, another take
LZMA - (Unofficial) Git mirror of LZMA SDK releases
nim_python_json
zlib-ng - zlib replacement with optimizations for "next generation" systems.
html2karax - Converts static html to Karax in Nim