Re: receiving POST encoded in JSON -- WEB400

Subject: Re: receiving POST encoded in JSON
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Mon, 1 Jun 2015 09:22:11 -0600
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Well, a staggering difference - using a 140kb JSON as a benchmark

JSON parse=16107ms; YAJL parse=53ms;

Thanks for sharing this. But the difference is so staggering that it can't
be an apples to apples comparison, or something else must be wrong. 16107ms
to parse 140K, just seems wrong.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: receiving POST encoded in JSON , Kevin Turner

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.