Does Json.NET Cache Serialization Information for Improved Performance?

JSON.NET cache serialized information to improve performance?

Overview

In the serialization of the object, check the field and attributes at runtime may be slow. Advanced libraries usually use IL emitting or expression trees to improve performance, but to build IL at runtime, you need to cache to reuse information of similar objects. This leads to the problem of cache strategy used by JSON.NET. Question

When the

method serialize the object of the attribute with json.net, will JSON.NET cache the access information of the members?

Answer JsonConvert.SerializeObject value Foo Yes. Foo JSON.NET can be serialized in the

class in its

class, especially and .

The cache mechanism IContractResolver DefaultContractResolver to maintain a global static example of a cache information. CamelCasePropertyNamesContractResolver

Use shared static tables between instances.

thread security

• These two contract parsers are safe threads to ensure that there will be no problems when sharing between threads. DefaultContractResolver
Custom contract parser
• CamelCasePropertyNamesContractResolver
If you create your own contract parser, you can cache only when reusing the contract parser instance itself.

Reduce memory consumption

If there is a memory limit, you can create a

local instance, use it for serialization, and then delete the reference to it.

Conclusion

json.net Effectively cache type serialized information to improve the performance during the serialization process, especially when processing large data sets.

The above is the detailed content of Does Json.NET Cache Serialization Information for Improved Performance?. For more information, please follow other related articles on the PHP Chinese website!