uWSGI lazy-apps with cheaper algorithm: undefined worker scaling behavior under load
I am tuning a uWSGI 2.0.x deployment that uses the cheaper algorithm to scale workers dynamically between a minimum and maximum count. I want to enable lazy-apps so each worker loads the application after forking, reducing shared memory and allowing the master to start before the app is loaded. The uncertainty is how these two features interact. With lazy-ap