MemoryPack
MessagePack for C# (.NET, .NET Core, Unity, Xamarin)
| MemoryPack | MessagePack for C# (.NET, .NET Core, Unity, Xamarin) | |
|---|---|---|
| 5 | 19 | |
| 2,806 | 5,288 | |
| 3.2% | 1.4% | |
| 8.8 | 7.2 | |
| 25 days ago | 7 days ago | |
| C# | C# | |
| MIT 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.
MemoryPack
- .NET 9 will be putting BinaryFormatter out to pasture
-
Godot + MemoryPack
I just stumbled over the serializer MemoryPack, which looks incredible.
-
Fury: 170x faster than JDK, fast serialization powered by JIT and Zero-copy
Given it's a binary serialization framework, it should not be too difficult, because the domain is well-explored and numerous libraries exist in C# which address same goals that Fury does.
More popular/newer examples are https://github.com/Cysharp/MemoryPack (which is similar to Fury with its own spec, C#-code first schema), https://github.com/MessagePack-CSharp/MessagePack-CSharp or even gRPC / Protobuf tooling https://github.com/grpc/grpc-dotnet
-
Native AOT Overview
With Unity/IL2CPP stuff: For general-purpose serialization libraries like JSON, you sometimes need to provide hints to make sure types are included: https://github.com/jilleJr/Newtonsoft.Json-for-Unity/wiki/Fi...
For schema serialization on known types, there are codegen tools (i.e. moc for MessagePack): https://github.com/neuecc/MessagePack-CSharp
MessagePack is migrating to Rosalyn code generators, so basically invisible codegen. Cysharp's newer serialization library, MessagePack, already uses this: https://github.com/Cysharp/MemoryPack
- GitHub - Cysharp/MemoryPack: Zero encoding extreme performance binary serializer for C#.
MessagePack for C# (.NET, .NET Core, Unity, Xamarin)
- .NET 9 will be putting BinaryFormatter out to pasture
-
Fury: 170x faster than JDK, fast serialization powered by JIT and Zero-copy
Given it's a binary serialization framework, it should not be too difficult, because the domain is well-explored and numerous libraries exist in C# which address same goals that Fury does.
More popular/newer examples are https://github.com/Cysharp/MemoryPack (which is similar to Fury with its own spec, C#-code first schema), https://github.com/MessagePack-CSharp/MessagePack-CSharp or even gRPC / Protobuf tooling https://github.com/grpc/grpc-dotnet
-
Native AOT Overview
With Unity/IL2CPP stuff: For general-purpose serialization libraries like JSON, you sometimes need to provide hints to make sure types are included: https://github.com/jilleJr/Newtonsoft.Json-for-Unity/wiki/Fi...
For schema serialization on known types, there are codegen tools (i.e. moc for MessagePack): https://github.com/neuecc/MessagePack-CSharp
MessagePack is migrating to Rosalyn code generators, so basically invisible codegen. Cysharp's newer serialization library, MessagePack, already uses this: https://github.com/Cysharp/MemoryPack
-
Dupes in bonelab?
Thanks, I'm sure I'll need it, though I do have my own platform with serialization set up already that I'm hoping I can port relatively easily (It's backended with MessagePack C# which is a lovely serializer for Unity.)
-
Does MessagePack-CSharp support OneOf type?
In the Road map of features #119 for MessagePack-CSharp, they checked the box for:
-
Dotnet API super slow?
Try MessagePack for serialization. It will help to reduce the size of the message and the time of serialization.
- Need persistent data across runs of your Unity game? Don't use PlayerPrefs for your game state! Here's how you can easily store your arbitrary game state in files instead.
-
Practice resources for handling and optimizing large game data sets?
I mentioned JSON, but there are many formats that are much more efficient. I can mention FlatBuffers, MessagePack and ProtoBuf. These are the ones I've used myself, and personally I'm most comfortable with MessagePack and ProtoBuf. I don't think the performance would be an issue if you had to choose between these three, it's mostly the API that is different.
- any good binary serializers that are not assembly dependent
-
LIVE: Otimizando aplicações .NET com MessagePack.
Biblioteca Nuget para C#
What are some alternatives?
fury-benchmarks - Serialization Benchmarks for fury with other libraries
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
janino - Janino is a super-small, super-fast Java™ compiler.
Protobuf.NET - Protocol Buffers library for idiomatic .NET
bridge-info - Information about SourceGear Bridge, a .NET Native AOT binding generator
Protobuf - Protocol Buffers - Google's data interchange format
corert - This repo contains CoreRT, an experimental .NET Core runtime optimized for AOT (ahead of time compilation) scenarios, with the accompanying compiler toolchain.
ZeroFormatter - Infinitely Fast Deserializer for .NET, .NET Core and Unity.
incubator-fury - A blazingly fast multi-language serialization framework powered by JIT and zero-copy.
Msgpack-Cli - MessagePack implementation for Common Language Infrastructure / msgpack.org[C#]
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
FlatSharp - Fast, idiomatic C# implementation of Flatbuffers