Add Lz4 or zstd compression to all serializations. Then compare their's time & output size.This item is of great significance to whether the serializer is suitable for transmission over long-distance Internet (obviously, the smaller the size, the better for the traffic).The purpose of testing the compressed size is to determine whether the serialized data they generate is suitable for compression.
Give up the .netframework,.net core,.net5-7 test. Just test the latest version and the last ltsc. For example, the current one is .net8. .net7 has expired and does not need to be tested. .net6 is the last ltsc. Although it is still in the support period, .net 8 is the new ltsc, so it does not need to be tested. If your test article is released later than .net9, you can consider testing with .net9.This can greatly reduce the workload.
Convenience of use. For example, MessagePackSharp needs to add some additional Attributes to Properties on class/struct to use, so it is not convenient.
If possible, it is recommended to add AOT test results.
At the same time, many serializers are cross-language, which is good, but this means that a public schema must be defined, which is not convenient for use in the two-side are both C# system.
Whether the serializer supports both classes&structs or classes-only .
A few small suggestions: