Node Js Php Serialize Array Code For Parsing

Using smaller field names can give you a 5-10 parsing performance boost and of course slightly smaller data packets being passed around.

Node Js Php Serialize Array Code For Parsing

Although originally derived from the JavaScript scripting language, JSON is now a language-independent data format and code for parsing and generating JSON data is readily available in many programming languages.

At Stackify, we use JSON extensively for REST APIs, serializing messages to queues, and much more.

We have compiled a list of some common JSON performance tips.

While we use.NET for most of our services, most of these tips apply to other programming languages as well.

You may need multiple JSON libraries for optimal performance and features In ASP.NET the most popular JSON library is Json.NET (Newtonsoft).

But ServiceStack, FastJsonParser (System.Text.Json) and even the built in DataContractJavascriptSerializer may be faster or provide specific features you may need depending on the scenario.

This is based on my own testing and I encourage you to do the same.

If you do a lot of parsing and really care about performance, FastJsonParser is a lot faster than anything else I have tried.

Here are my results from doing some simple benchmarks from a test app ( View on GitHub ).

Fastest serializer: ServiceStack Fastest parser: FastJsonParser Overall most features and flexibility: Json.NET I havent tested it myself but I have also heard good things about Jil which is designed entirely for speed by StackExchanges team.

Use streams whenever possible Most JSON parsing libraries can read straight from a stream instead of a string.

This is a little more efficient and preferred where possible.

Compress your JSON Since JSON is just simple text, you can expect to get up to 90 compression.

Avoid parsing JSON if you dont need to This may seem obvious, but it necessarily isnt.

For web apps that receive JSON and simply write it to a queue, database, or other storage, try not to ever parse the JSON if you can.

When using something like ASP.NET Web API, dont define your methods expecting specific classes as incoming data and instead read the post body so ASP.NET never parses the JSON.

For Stackifys services we use header values for authentication, so in some scenarios, we never even need to analyze the body of the message.

In the first version of our code, we were looping through the array and kept serializing one log messages at a time because the final output could only be up to a certain size to queue.

We were able to do some optimization of this logic and it made a pretty significant difference in server CPU usage.

Use pre-defined typed classes If at all possible, make sure you have a class that matches the JSON structure you are working with.

Parsing generic JSON to a JSON.net JObject or generic dictionaries with FastJson is slower (20) than reading that data in to a defined class type.

This is likely because a lot more meta data is tracked with the generic Json.NETs JObject, JArray, JValue objects.

Newtonsoft.Json.JsonConvert.DeserializeObject (jsonData); faster with typed object.

Newtonsoft.Json.JsonConvert.DeserializeObject(jsonData); slower with generic JObject result.

In some scenarios you may also want to configure various special settings as well.

Find info about Web API serialization settings here.

Dont serialize all fields, null or default values Check your JSON library settings to see how you can ignore specific fields, omit null values, etc.

Most.NET libraries will use DataContractDataMember attributes and settings.

Get Json.Net docs on the subject here.

Use shorter field names Most libraries enable you to specify attributes on your classes to override the names of the fields as they are being serialized.

This can allow you to make your field names much smaller when serialized but more human readable in your code.