Using async gevent worker. Huge oversight for "CTO Outsourcing."

[knappador]

No description provided.

[tarekziade]

it's a cpu-bound task. gevent won't make a difference for this specific hello app

[knappador]

Then do it for the DB test and use Psycopg2 with any one of the green
solutions that won't block on DB access. Is there any GOOD reason not to
use the -k switch? Absolutely not.

On Fri, Mar 29, 2013 at 9:56 AM, Tarek Ziade notifications@github.comwrote:

it's a cpu-bound task. gevent won't make a difference for this specific
hello app

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

[knappador]

I highly doubt that the app was CPU bound given all of the middlewares left turned on for no good reason. Sessions by themselves are very heavy in the current configuration if only because the DB requests (no session write-through-caching enabled either) will tank performance. We're talking about at least an order of magnitude for a small app that doesn't need any DB requests when just serializing JSON's. This whole benchmark was just silly. If they were going to not enable any features of the light-weight-by-default frameworks, they should have turned off the unneeded features of Django.