Feedback regarding the test suite - ideas how to improve it about serializertests HOT 2 CLOSED

• Regarding Benchmark.NET I have mixed feelings about it. It is nice for micro benchmarks but the serializer tests are not really micro benchmarks. I explictely want to test O(n) behavior. For that I need many invocations of a method with different parameters. I prefer a real profiler which has nearly zero overhead like ETW where I get GC, excpetions, VirtualAlloc and such all for free and I can later drill into the data to compare the serializers not only by the timing but also why a specific method was slow.

• I have added with commit d260a7f also some reference tracking tests which contain interesting results.
  see https://aloiskraus.wordpress.com/2018/05/06/serialization-performance-update-with-net-4-7-2/
  The ReferenceBookShelf contains a dictionary of DateTime objects which share the same string reference.
  That should bring nearly all types you wanted to see as well (at least floats).
  This test did show that FastJSON cannot round trip DateTime objects and JIL cannot cope with Dictionaries having DateTime objects as keys.

• The article table formatting is fixed now. The crazy wordpress template is always squishing my tables.

• The updated article should address the other missing information now as well.

Is the current state sufficient for you now? The goal is that you can use the project and try some new serializers with your custom objects out to see if the performance is so good or not. Bringing many more tests for different data types is in my opinion of no use since you will quickly run into graph and information overload. It is better to try your specific objects with the test suite and check for yourself.

from serializertests.

I will close this one. Good idea for the requirement table if the serializer can serialize private fields, properties, .. . This will be really useful.

from serializertests.