Choosing between a fixed uWSGI worker pool and the cheaper subsystem
Decide when to use a fixed uWSGI worker pool versus the cheaper dynamic scaling subsystem for Python WSGI apps.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide when to use a fixed uWSGI worker pool versus the cheaper dynamic scaling subsystem for Python WSGI apps.
Idle workers waste RAM. Discover how uWSGI’s cheaper subsystem dynamically scales worker processes, saving memory while keeping performance high.
Prevent unresponsive Python workers by implementing uWSGI master mode and harakiri timers to automatically detect and restart stalled processes.
Deploy and maintain several Python web applications on a single server using uWSGI Emperor mode. Learn how to set up the emperor, configure vassals, verify operation, and recover from failures with minimal downtime.
Run one WSGI app under uWSGI Emperor with cheaper autoscaling, lazy-apps, harakiri, and Nginx. Includes vassal configuration, load testing, and recovery steps.
Learn how enabling lazy-apps defers Python import until the first request, reducing per‑worker RSS and when to watch out for fork‑unsafe code.
Manage multiple isolated Python applications on a single host using uWSGI Emperor mode. Learn how to configure vassals, secure the supervisor, and monitor your fleet.
uWSGI's cache2 directive caches full WSGI responses in-process, keyed by path and method. Here's a minimal setup, how to verify hits, and the staleness and key-collision traps to avoid.
Learn how to run multiple Python web apps from a single uWSGI Emperor, achieve zero‑downtime reloads, and keep your deployment simple and reliable.