gunicorn multithreads
There is a performance issue with production deployment of smasch: fetching single request that takes several seconds blocks all other requests. As far as I can tell it's because gunicorn is running on single thread/process/worker. Here is our production config: https://gitlab.lcsb.uni.lu/NCER-PD/scheduling-system/-/blob/master/debian-files/smasch.service#L11
The easiest solution is to add workers:
-w WORKERS, --workers=WORKERS - The number of worker processes. This number should generally be between 2-4 workers per core in the server. Check the FAQ for ideas on tuning this parameter.
Do you have experience with multiple gunicorn workers. I see that there are different type of gunicorn workerks (-k WORKERCLASS, --worker-class=WORKERCLASS
). I remember that @jacek.lebioda was doing some tests, but don't remember conclusion.
@carlos.vega