ResonantGeoData / RD-OpenGeo

Resonant GeoData primary deployment
https://www.resonantgeodata.com
Apache License 2.0
5 stars 3 forks source link

Figure out the appropriate size for larger Heroku Dynos #4

Closed brianhelba closed 2 years ago

brianhelba commented 3 years ago
From https://devcenter.heroku.com/articles/dyno-types , the important differences are: Dyno Type Memory (RAM) Relative Compute Performance $ / month $ / year
hobby 512 MB 1x-4x $7 $84
standard-1x 512 MB 1x-4x $25 $300
standard-2x 1024 MB 4x-8x $50 $600
performance-m 2.5 GB 11x $250 $3000
performance-l 14 GB 46x $500 $6000

Generally, a Django web server should typically not require over 512MB to run. Workers may require more than this, but we want to deploy those to EC2 instead, which has more favorable memory balances and GPU support. One possible source of memory bloat could be the side effects of importing third party modules. Rather than doing these imports at the file level, where the web server will also import them, they could be done only within the functions that actually need them, which will practically only be executed by the worker.

banesullivan commented 2 years ago

This issue is here for reference. Closing