...
Our small/reasonable requests are somewhat slower on heroku than current infrastructure. But our larger requests are much slower, with and worse much more variance in speedresponse time, sometimes pathologically. Apparently very slow requests--and/or requests which create a lot of objects/use a lot of RAM--cause heroku performance to degrade unpredictably? We could try to diagnose and improve our slowest actions, but this raises concerns about increasing difficulty of app development.
Also accessing some of these most problematic pages actually causes the ONE worker to exceed maximum memory on the 512MB dyno. :(
Action | Current infrastructure | heroku (hobby dyno) |
|---|---|---|
work, 694 children (4b29b614k, Ramellli) | 2-3s | 3.5-6s, but sometimes as high as 7 or 9!! |
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 |
Tuesday Oct 6
For future: Asset delivery
...