wtf is ey-passenger-tweaks?

If your web application has high memory needs and keeps crashing because the hosting platform thinks it's using too much RAM, this project can help. It's a recipe designed for Engine Yard Cloud that lets you adjust how many background workers are running and raise the memory threshold so your app won't get killed for using too much. At a high level, the recipe does two things: it reduces the number of Passenger workers (the processes that handle incoming web requests) and increases the memory limit that the monitoring system enforces. By cutting back on workers, you free up memory that can instead be allocated to the app itself. You customize a few variables at the top of a configuration file to specify your app name, how many workers you want, and your desired memory limit. This is meant for someone hosting a single memory-hungry application on Engine Yard who keeps running into crashes. For example, if you have a data-heavy Rails app that needs more RAM per request, reducing the worker count gives each remaining worker more memory headroom. It's essentially a proof of concept rather than a production-grade tool. There are a few notable trade-offs. Because it reduces the number of workers available to handle requests, it's not advisable for multi-app environments where you might end up with too few workers to serve your traffic. The recipe also restarts the web server (Nginx) twice on every configuration run, which could cause brief interruptions. If frequent restarts are a problem for your setup, you'd need to dig into more advanced custom configuration to avoid that side effect.