-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entries page performance #77
Comments
These two different runs of bench.py (on a different laptop) show that:
This probably means that there are no quick gains to be had (aside from running on pypy, but that's not an app improvement). Remaining options I can think of:
|
The following confirm that the huge time I got initially with curl for the instance was most likely due to network slowness. Also, it turns out the run on the original laptop was done with FLASK_DEBUG=1, which added about 2s to the /?show=all curl.
|
This gist shows that using generate()/stream() instead of render() does decrease the time it takes to get the first 100kb of the page (as expected). |
This looks good enough for now. Will only implement pagination if it gets much worse.
|
The entries (main) page takes too much time to load.
Some of that is due to get_entries() being slow, but most of the time seems to be spent rendering the page.
On my laptop:
On a t2.micro EC2 instance (update: these might be due to bad internet, as it improved later):
The text was updated successfully, but these errors were encountered: