10 ms·
> ... getting a small... temporary virtual server in which > a limited number of processes run, often just one. Is it "often just one" process running becau
by jt2190 13y ago
> ... getting a small... temporary virtual server in which
> a limited number of processes run, often just one.
Is it "often just one" process running because of some limit enforced by Heroku, or is it simply because, well, many people don't bother to spawn additional processes? Do additional processes "wait" for other processes to finish before proceeding? (I'm about to run another experiment on Heroku...)
- jschulenklopper 13y agoHeroku enforces a 512 MB memory limit (or 1024 MB on the 2X dynos), so that limits the practical number of processes running in the same dyno... especially if those are (heavy) full-stack web applications. Additionally, processes share the same CPU, so you'll not get the same performance as two processes in their own dynos. See https://devcenter.heroku.com/articles/process-model https://devcenter.heroku.com/articles/process-model and https://devcenter.heroku.com/articles/rails-unicorn https://devcenter.heroku.com/articles/rails-unicorn. Unicorn forks multiple OS processes within each dyno to allow a Rails app to support multiple concurrent requests. Generally no more than 3-4 processes will fit in one dyno.