It has been a few years since, but I wrote a standalone small Rails app for an internal service for a company that also runs a giant Rails app for their main bu

It has been a few years since, but I wrote a standalone small Rails app for an internal service for a company that also runs a giant Rails app for their main business. I ended up heavily tuning the ruby GC parameters, which reduced the final resource usage of the app especially over longer continued use nearly tenfold. There is a lot to gain if you know the actual object and memory limits your app needs for it's core usage rather than letting Ruby allocate more and more memory. Caveat is that was a long time ago with Ruby ~2.3 and things have certainly changed and probably improved by now. That service has been as stable as one could hope. It just runs in a docker container on a dedicated machine that's also used for other development purposes and consumes a couple of hundred MB of ram. The number of times it was down in the past ~6 years can be counted on one hand.