...
Action | Current infrastructure | heroku (hobby dyno) |
|---|---|---|
work, 694 children (4b29b614k, Ramellli) | 2-3s | 3.5-6s, but sometimes as high as 7 or 9!! |
viewer_images_info json for 694 children | 1.2-3s (not sure why the variance) | 1.4-3s (don’t know why this one matches heroku) |
work, 115 children (ysnh5if, chemical atlas) | 1-1.5s | 1-2s but occasionally as high as 3s |
work, 5 children (sb3979577, Arcana Naturae Detecta) | 1.2s (somehow sometimes as low as .2s?) | 1.2s (also sometimes somehow as low as .2s?) |
Fixity report page | 4.7-5s | 8s, sometimes as high as 15s |
Weird that some of the smaller pages have similar performance, but the big ones get really bad. Not sure what’s going on. We could try “jemalloc” ruby build on heroku but not sure that’s going to be it. Various other optimizations we could try, but are we accepting increased need to optimize and thus increased difficulty level of development on heroku?
Tuesday Oct 6
For future: Asset delivery
...