Journal of heroku investigations. Most recent entries on top? See also Heroku Consideration
Wed Oct 14
For RAM comparison, on our current EC2 production, after being up for some time, passenger reports this memory use:
| Code Block |
|---|
------ Passenger processes ------
PID VMSize Private Name
---------------------------------
18108 299.2 MB 2.0 MB Passenger watchdog
18114 1082.6 MB 5.3 MB Passenger core
18139 30.4 MB 0.4 MB /usr/local/lib/ruby/gems/2.6.0/gems/passenger-5.3.7/buildout/support-binaries/PassengerAgent temp-dir-toucher /tmp/passenger-standalone.11jhb2e --cleanup --daemonize --pid-file /tmp/passenger-standalone.11jhb2e/temp_dir_toucher.pid --log-file /opt/scihist_digicoll/shared/passenger.log --user digcol --nginx-pid 18123
18187 958.4 MB 340.2 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18206 873.4 MB 281.1 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18225 738.5 MB 197.3 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18244 736.6 MB 160.8 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18261 736.7 MB 158.1 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18278 736.8 MB 169.9 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18295 736.9 MB 163.0 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18312 737.0 MB 169.8 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18329 737.1 MB 163.2 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...)
18346 737.2 MB 162.4 MB Passenger AppPreloader: /opt/scihist_digicoll/current (forking...) |
So actually it’s true that the Private RSS was getting up to 340MB, although after more use. One difference is that on heroku it seems to balloon up memory quicker. But I may have under-estimated our RAM use – although it still isn’t the 400-500MB+ that we’re seeing in heroku.
Monday Oct 12/Tuesday Oct 13
...