Comments on: JSON Decoding Speed Comparison

By: Shea Frederick

Shea Frederick — Thu, 11 Mar 2010 20:28:22 +0000

Lower is better, the measurement is milliseconds per 1000 repetitions.

By: MrRoyce

MrRoyce — Thu, 11 Mar 2010 16:29:51 +0000

? What is the measurement for the values on the X axis? Is lower better? Is it trans/sec,? Not sure how to understand the data without a label telling what data is being shown???

By: What’s the Word – Meetup Videos and More | VinylFox

What’s the Word – Meetup Videos and More | VinylFox — Wed, 03 Feb 2010 17:36:10 +0000

[...] Should be some interesting results, which ill be posting a summary on soon. My first test was for JSON decoding speed, which I posted results for a couple of weeks [...]

By: Shea Frederick

Shea Frederick — Fri, 15 Jan 2010 18:09:50 +0000

I already noted that eval is unsafe in the post, along with my reasoning for not testing a json decoding library. This post has nothing to do with ‘safe’ methods.

I disagree that the result was “expected”, since native JSON has the requirement of safely decoding JSON, the expectation is that would take longer than the other unsafe methods. This was the assumption of many people that I discussed this with before starting on these tests.

Thanks for the tip on leaving off the new operator, though I agree that it likely would not have changed the test results.

By: Andrea Giammarchi

Andrea Giammarchi — Fri, 15 Jan 2010 17:55:02 +0000

nice post, kinda expected tho. First of all, eval in that way is unsafe. You should compare json2.js from Mr D. and see how things go with all those “let’s see if it’s safe” RegExps.
Secondly, there is no reason on earth to use new in front of Function since whatever function that returns an instance of object, does not need new in front of it. In few words, the usage of new Function creates an instance that is completely useless.
Example:
function Function(){
// here we got an instance that will never be use
return function () {};
// overload the returned value, not “this” but the function
};

new Function();
Function();

I am sure that this won’t make any consistent difference in above results in any case, but specially when Firebug is enabled and we need to handle big results, Function does not pass throught the console, so I usually appreciate this to avoid problems/massive delays while debugging.

Regards

By: Shea Frederick

Shea Frederick — Tue, 12 Jan 2010 16:19:55 +0000

All versions that support native JSON, which is 3.1 and up. This test was in the wild, so it includes any version that is still in use.

Remember that native JSON decoding requires that it be 100% valid JSON. Run your JSON through http://www.jsonlint.com to find out.

By: mdmadph

mdmadph — Tue, 12 Jan 2010 16:06:01 +0000

What version of Firefox were you using there?

And I still can’t get MSIE 8.0′s native JSON to work. Though, I see documents about it on the web, so I know it’s just me.

By: uberVU - social comments

uberVU - social comments — Tue, 12 Jan 2010 16:03:17 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by VinylFox: New blog post about JSON decoding speed in JavaScript – http://bit.ly/5Ksgy7 – interesting results….