3 ms·
Are your dozen web apps large, featureful code forge systems?
by gtaylor 11y ago
Are your dozen web apps large, featureful code forge systems?
- maratd 11y agoNo, they're not. That said, there is no valid engineering reason why any web app should require more than 512MB of memory to run with minimal user load. User load is what bumps up the RAM requirements. If the active user count is in the single digits and you're running into problems with RAM, either something is deeply misconfigured on your server, you have a ton of data, or the codebase is poor.
- chrisseaton 11y agoWhat if your web app manages a data structure that is simply larger than 512 MB? Like analytics data or something like that.
- maratd 11y agoPlease read what I wrote again. I specifically mentioned a large data set.
- deleted 11y ago[deleted]
- gtaylor 11y agoWow, that's a lot of blanket statements. Nevermind the fact that GitLab won't even have a full 512 MB at its disposal in your particular case (the $5 512 MB droplet). Memory is cheap. GitLab's resource usage doesn't increase much from the baseline as you go from 1 user to 100 users. You just can't run it on a potato.
- sytse 11y agoAn empty Rails app is already 100MB+ or memory. GitLab is running the largest open source rails app. Also, since we use Unicorn instead of multithreading we have to spin up multiple Rails apps.
- charliesome 11y ago>That said, there is no valid engineering reason why any web app should require more than 512MB of memory to run with minimal user load. GitLab (and every other Rails app) makes the assumption that it's better to eager load an entire codebase once at boot time rather than to load code on demand and throw it away during a request. That trades off baseline memory usage for runtime performance, and it's a perfectly valid 'engineering reason' for why GitLab's baseline memory usage is so high.
- nadams 11y agoSrchub runs on 512MB of RAM currently using 150MB of RAM. I currently host 173 projects.