Json.NET Claims Significant Performance Improvements over Other .NET Serializers
- Share
-
- |
Read later
Reading List
JSon.NET is claiming to offer better serialization and deserialization performance than any of the major serializers in .NET including BinaryFormatter. It even performs well against the remarkably fast DataContractSerizalier.
It is no shock that someone was able to beat the somewhat troubled WCF JSON implementation. Not only is it the only library in the benchmark that was slower at serialization than deserialization, its serialization actually takes 6 times longer than its deserialization. The real shocker from the benchmarks is that the BinaryFormatter is relatively slow. Most people would generally assume binary formats are faster, but in these benchmarks both JSON.NET and WCF’s DataContractSerializer are nearly twice as fast at deserialization and easily three times faster at serialization.
The benchmark results are available on James Newton-King’s blog. Json.NET is being released on CodePlex under the MIT License.
Rate this Article
- Editor Review
- Chief Editor Action
Submit
Submit
Related Sponsor
Get a holistic view of your entire business infrastructure with Site24x7's all-in-one monitoring solutions. Try Site24x7 for a unified experience.
Hello stranger!
You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think
Community comments
Still lacks the ease of using attribute based Json conversion
by
Binoj Antony
Posted
Still lacks the ease of using attribute based Json conversion
by
Binoj Antony
The price you pay for the performance is to do the serialization manually, the default attribute based Json conversion is more elegant readable and less-effort-taking any day when implementing WCF services.
Also what if we want to support Json plus the default SOAP/XML, here again we have to manually handle this condition.
Also what if we want to support Json plus the default SOAP/XML, here again we have to manually handle this condition.
