MemoryPack
corert
MemoryPack | corert | |
---|---|---|
5 | 8 | |
2,806 | 2,863 | |
3.2% | - | |
8.8 | 8.3 | |
25 days ago | over 3 years 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#.
corert
-
Native AOT Overview
An explanation of the problem: https://github.com/dotnet/corert/blob/master/Documentation/u...
-
Thinking about zero-allocation parsing.
Memory was not really designed for having lots of instances of it and doing intensive computations/searches on the instances. The reason for it is that Memory.Span property is actually quite expensive to call. Memory is a union type for storing strings, arrays, and even handles to native memory. Every time you construct it , slice it, or retrieve it's span, lost of machinery related to this union has to run. For example see the source for the Memory.Span property: https://github.com/dotnet/corert/blob/master/src/System.Private.CoreLib/shared/System/Memory.cs#L285.
-
Is there any good obfuscator or obfuscation algorithm that makes following the logic difficult?
For earlier versions, try https://github.com/dotnet/corert
- What are the features you're looking forward to in the next version of Fsharp?
-
Preview Features in .NET 6 - Generic Math
Yeah I know it's slower on its own, but I was sure it was handled as a faster intrinsic by the runtime. Went to double check and realized I was actually mixing things up with what CoreRT did (see here) but I guess it doesn't apply to CoreCLR. Would be surprised if there weren't any specific optimizations for this with .NET 6+ though, or at the very least with NativeAOT (given they've been porting some bits over from CoreRT and .NET Native too). Will need to go gather more info on this, as it's pretty interesting 🙂
-
Awesome .NET Performance
> AOT compilation? I'll believe it when they'll release it, until then, it's all speculation
Devil's in the details, but there -is- AOT compilation[0]. While it hasn't been released as an official product, it has been used for a few projects including a commercial game [1]. And yes, they're looking into the next steps to make it a 'released' thing.[2]
[0] - https://github.com/dotnet/corert/
[1] - https://github.com/dotnet/corert/issues/8233#issuecomment-65...
[2] - https://github.com/dotnet/runtimelab/tree/feature/NativeAOT
-
What the F#
That is a well known issue, also what prevented F# to be properly used in .NET Native.
https://github.com/dotnet/corert/issues/5780#issuecomment-40...
-
"Low Level" questions about C# (and .Net)
CoreRT
What are some alternatives?
fury-benchmarks - Serialization Benchmarks for fury with other libraries
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
janino - Janino is a super-small, super-fast Javaâ„¢ compiler.
awesome-dot-net-performance - A curated list of awesome .NET Performance books, courses, trainings, conference talks, blogs and most inspiring open source contributors. Inspired by awesome-... stuff.
incubator-fury - A blazingly fast multi-language serialization framework powered by JIT and zero-copy.
obfuscar - Open source obfuscation tool for .NET assemblies
bridge-info - Information about SourceGear Bridge, a .NET Native AOT binding generator
.NET port of LMAX Disruptor - Port of LMAX Disruptor to .NET
jvm-serializers - Benchmark comparing serialization libraries on the JVM
fsharp-companies - Community curated list of companies that use F#
elmish - Elm-like abstractions for F# apps