- From: Konstantinov Sergey <twirl@yandex-team.ru>
- Date: Mon, 12 Aug 2013 09:46:03 +0400
- To: Noah Mendelsohn <nrm@arcanedomain.com>, "www-tag@w3.org" <www-tag@w3.org>
- Cc: "dlee@marklogic.com" <dlee@marklogic.com>
The paper looks very good, but it's obviously incomplete as it doesn't test JSON parsing speed using JSON.parse. I don't know exactly how fast is JSON.parse compared to eval, but JSON is just some subset of JS syntax and it might be parsed faster. 12.08.2013, 05:24, "Noah Mendelsohn" <nrm@arcanedomain.com>: > David Lee has written an interesting analysis of JSON vs. XML performance. > There's lots of detail and (seamingly) very careful measurements. From the > conclusion section: > > "Given the same document object, one can produce nearly identical sized > JSON and XML representations. Network transfer speed is directly related to > the document size so is unaffected by the markup given similar size. > Compressed documents in all formats even very "Fat" representations of JSON > or XML compress to nearly identical size which is an indicator that they > contain approximately the same entropy or information content and > transferring these documents to a wide variety of devices takes effectively > the same time per device. Parsing speed varies on the technique used. Pure > JavaScript parsing generally performs better with XML then with JSON but > not always, while Query speed generally is faster for JSON, but again, not > always. Overall using native JavaScript the use of XML and JSON is > essentially identical performance for total user experience (transfer plus > parse plus query), however use of the popular JavaScript library jQuery > imposes a steep penalty on both JSON and XML, more-so for XML. [4]" > > The whole paper is well worth reading IMO. > > Noah > > [1] > http://www.balisage.net/Proceedings/vol10/html/Lee01/BalisageVol10-Lee01.html -- Konstantinov Sergey Yandex Maps API Development Team Lead http://api.yandex.com/maps/
Received on Monday, 12 August 2013 05:46:33 UTC