Converting from httpd.conf:processes/threads to uwsgi.ini:workers/threads

ngkabra

For my django app on Webfaction, after experimentation I had found processes=20 threads=4 to be the right configuration. (On the webfaction machine, I had a 2GB account, and /proc/cpuinfo showed 4 processors)

Now I'm migrating that app to opalstack/nginx and I assume I should use the workers and threads values in uwsgi.ini. Any suggestions on what are reasonable values I can start with to get similar memory-usage vs performance characteristics?

I understand that there might not be a direct one-to-one correspondence; just looking for any rules of thumb, or a starting point. I can then monitor and adjust later, but would like to start in the correct general area.

ngkabra

Or should I be trying something like cheaper-algo = busyness and related settings?

sean

If you were using processes=20 threads=4 in your mod_wsgi config at WF, then 20 workers and 4 threads in your uwsgi config would be a reasonable place to start.

I've not tried the cheaper subsystem parameters myself yet.

ngkabra

Thanks. I'll try that and report back here if my experimentation reveals anything interesting.