Integer overflow check slows down json parsing

[Kurt Griffiths]

Currently we hook json parsing to check for integer overflow, but this slows down simplejson.

[Kurt Griffiths (kgriffs)]

Overhead has not been measured yet, right? Also, not that with pypy this isn't so much of an issue since you don't have to thunk back to python from C.

[Zhihao Yuan (zyuan)]

pypy is fine only if we detect pypy and switch to std json in that case. At this point of time, I suggest to limit the usage of simplejson.

[Kurt Griffiths (kgriffs)]

I don't mind dropping simplejson. Wrt Python 2.6, we can be 2.6 *compatible* but saying that it won't give you the best experience (since stdlib json on 2.6 is pretty slow).

[Kurt Griffiths (kgriffs)]

simplejson has been dropped now.

[Kurt Griffiths (kgriffs)]

supporting msgpack and having clients default to using it would mitigate this.

[Victoria Martinez de la Cruz (vkmc)]

There is a blueprint that covers this bug. More details in https://blueprints.launchpad.net/marconi/+spec/api-v1.1-msgpack.

[Flavio Percoco (flaper87)]

In [27]: timeit json.loads(doc)
100000 loops, best of 3: 5.32 µs per loop

In [28]: timeit utils.read_json(StringIO.StringIO(doc), len(doc))
10000 loops, best of 3: 19.7 µs per loop

[wangxiyuan (wangxiyuan)]

We have "msgpack" with websocket already. https://review.openstack.org/#/c/256978/
Next step is for "webhook"