3 ms·
https://github.com/pallets/flask https://github.com/pallets/flask https://github.com/pallets/jinja https://github.com/pallets/jinja 0% C Also 800 ms is NOT a
by hmnom 7y ago
https://github.com/pallets/flask https://github.com/pallets/flask
https://github.com/pallets/jinja https://github.com/pallets/jinja
0% C
Also 800 ms is NOT a reasonable response time to generate what basically is a bunch of text, that is absurd, but I guess this is the baseline in 2019.
I trust all IO is cached. The author can confirm it. This is just how slow Python is.
- wyldfire 7y agoSwitching to PyPy is likely to improve the overall performance if it's not database or I/O bound.
- ignaloidas 7y agoAlmost none of the IO of that page is cached actually[0]. The only thing I'm sure that is cached is the templates themselves. I'm pretty sure that neither git lookups, nor DB accesses are cached, where you can save time. And mind you, this is served from a single data center in USA, and the latency can already eat up a lot of that. I in Europe have 300ms ping to it, so it might be that you are simply far away from the physical location. [0] https://git.sr.ht/~sircmpwn/git.sr.ht/tree/master/gitsrht/blueprints/repo.py#L136 https://git.sr.ht/~sircmpwn/git.sr.ht/tree/master/gitsrht/bl...