Using stock json and improved query. Query might be cheating.

[knappador]

I do better work than these guys on Django.  Hire me instead of "CTO Outsourcing."  I actually know how to work with Django as well as optimize deployments.

[aidanhs]

Pretty sure this won't work as-is, it needs a closing curly brace on line 13.

[sp1d3rx]

agreed, doing tests on my system, running 30000 iterations:
json: 1.86270008792
simplejson: 2.0614045791

so, json runs in 90% of the time it takes simplejson, or a 10% improvement.

[knappador]

https://gist.github.com/wmark/1379050

Requesting ujson. C-extensions are a strength of Python, and this is a
totally legitimate use case.

On Mon, Apr 8, 2013 at 12:38 PM, sp1d3rx [email protected] wrote:

agreed, doing tests on my system, running 30000 iterations:
json: 1.86270008792
simplejson: 2.0614045791

so, json runs in 90% of the time it takes simplejson, or a 10% improvement.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/21#issuecomment-16065829
.

[pfalls1]

We're now using ujson instead of simplejson.

For the query, we'd like to keep it as n-queries, rather then 1 query requesting n-rows.