Hacker News Reader

Comment by TekMol | Hacker News Reader

    Estimated Response Times
    100-300ms Django with warm cache
    500ms-2s Django with cold cache

That sounds very slow to me.

How do these numbers compare with other popular frameworks like Laravel, Symfony, Flask, nextjs ... ?

I for one use my own PHP framework (own routing, templating engine, db abstraction) and see response times of about 40ms.

View on HN

It really depends on the workload here. It is possible that there's a large CPU-bound workload (e.g. a join-heavy sql query) that would throw these numbers off.

But yeah, these numbers are pretty bad for a simple templating job in Django, even taking into account network round-trip time.

I get roughly 46ms from a cheap distant vps with no particular care for performance in my Django app so these numbers are strange.

on a laptop in 2014 with a poorly configured mysql instance, these numbers are about right

Somehow I managed to miss the obvious warning... thanks !

Yes, this is too slow. You can definitely go faster with Django.

Reply on news.ycombinator.com