mk48
rust_serialization_benchmark
Our great sponsors
mk48 | rust_serialization_benchmark | |
---|---|---|
4 | 22 | |
304 | 512 | |
4.9% | - | |
4.9 | 7.7 | |
5 months ago | about 19 hours ago | |
Rust | Rust | |
GNU Affero General Public License v3.0 | - |
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.
mk48
-
Announcing bitcode format for serde
We use our own custom game engine.
- Mk48.io - Multiplayer Naval Combat Game made with SvelteKit.
-
Drop your underrated games too!
mk48.io (PC only, but does work on mobile, PC still recommended)
-
I think there need to be a tier 10 destroyer and cruiser and corvette
For the time being, I've added your suggestions to our list of ships to consider. For reasons I have stated above, they would probably considered for more appropriate levels under 10.
rust_serialization_benchmark
-
Rkyv: Rkyv zero-copy deserialization framework for rust
https://github.com/djkoloski/rust_serialization_benchmark
Apache/arrow-rs: https://github.com/apache/arrow-rs
From https://arrow.apache.org/faq/ :
> How does Arrow relate to Flatbuffers?
> Flatbuffers is a low-level building block for binary data serialization. It is not adapted to the representation of large, structured, homogenous data, and does not sit at the right abstraction layer for data analysis tasks.
> Arrow is a data layer aimed directly at the needs of data analysis, providing a comprehensive collection of data types required to analytics, built-in support for “null” values (representing missing data), and an expanding toolbox of I/O and computing facilities.
> The Arrow file format does use Flatbuffers under the hood to serialize schemas and other metadata needed to implement the Arrow binary IPC protocol, but the Arrow data format uses its own representation for optimal access and computation
-
Comfy Engine 0.3 - No Lifetimes, User Shaders, Text Rendering, 2.5D, LDTK
Nice that comfy gets even easier. Also, if serde's compile time is an issue, then there's nanoserde which is usually much much faster according to benchmarks
-
Müsli - An experimental binary serialization framework with more choice
A note on performance and size: Some benchmarks and statistics are included in the README. But only because people will be curious. I've based my methodology on rust_serialization_benchmark, but decided to not extend it (for now) since it seems to exclude any Rust types which are not widely supported by all formats being tested (like HashMap's and 128-bit numbers). The test suite is already quite nice if you want to take it for a spin.
-
bitcode 0.4 release - binary serialization format
While we haven't benchmarked either of those ourselves. You can checkout rust_serialization_benchmark which has protobuf under the name prost.
-
Announcing bitcode format for serde
Update: Benchmark PR submitted: https://github.com/djkoloski/rust_serialization_benchmark/pull/37
-
Best format for high-performance Serde?
Here is a speed and size benchmark of different rust binary serialization formats: https://github.com/djkoloski/rust_serialization_benchmark Warning: I think the creator of this benchmark is also the creator of rkyv, one of the best positioned formats in the benchmark.
-
Grammatical, automatic furigana with SQLite and Rust
So I assume you're deserializing them before processing the book? If so then if you want an easy speed-up you could also take a look at these benchmarks and pick a faster serialization crate. (: (Although you might or might not get a big speedup; depends on what exactly you're deserializing and how much you are deserializing.)
-
GitHub - epage/parse-benchmarks-rs
You can add the rust serialization benchmark to that list
-
The run-up to v1.0 for Postcard
Hey! Similar to bincode, it provides a very similar, compact binary format. The rkyv benchmark is the most comprehensive I'm aware of, but compared to bincode, postcard is generally a similar speed for serialization or deserialization (maybe a touch slower), but generally produces a slightly smaller "on the wire" size.
-
I made a blazing fast and small new data serialization format called "DLHN" in Rust.
You should add your crate to these benchmarks. (Which are, AFAIK, the most comprehensive set of benchmarks currently available for Rust serialization libraries.)
What are some alternatives?
rust_rpg_toolkit - Engine / framework for creating highly customizable and user modable action RPG's
json-benchmark - nativejson-benchmark in Rust
flux - An open-source tribute to the macOS Drift screensaver
rust-serialization-benchmarks
conwayste - Multiplayer Conway's Game of Life (desktop app + server) implemented in Rust
bebop - 🎷No ceremony, just code. Blazing fast, typesafe binary serialization.
vach - A simple archiving format, designed for storing assets in compact and secure containers
unsafe-code-guidelines - Forum for discussion about what unsafe code can and can't do
capstone - Sci-fi run 'n' gun action RPG created in Rust, using Macroquad [Moved to: https://github.com/olefasting/rust_rpg_toolkit]
dlhn - DLHN implementation for Rust
fluid-simulation-rust - A rewrite of my fluid simulation project entirely in Rust
bincode - A binary encoder / decoder implementation in Rust.