5 ms·
High Performance Django
- TekMol 5y agoEstimated 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.
- sgt 5y agoYes, this is too slow. You can definitely go faster with Django.
- guggle 5y agoI get roughly 46ms from a cheap distant vps with no particular care for performance in my Django app so these numbers are strange.
- yen223 5y agoIt 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.
- develatio 5y agoThis seems to be from 2014, the code is completely outdated.
- ashconnor 5y ago> We originally released High Performance Django in 2014 following a successful Kickstarter campaign. While the packages and code samples may now be outdated, we stand by the general concepts and still use them in production sites today.