-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python simultaneously worker launch #832
Comments
Hi @TheFatal atm this is the way it is / was implemented but we are sure there is some space for improvement. I will flag this as an enhancement and chat with our engineering team about it and update this issue as we go. Are you available for testing any patches we will come along with? |
thanks tou for the reply, for sure i can test some patchs on my app |
Same issue on our end. It also cause some issues for some benchmark testing: TechEmpower/FrameworkBenchmarks#8059 |
Possibly related to #794. |
@tippexs any news on this issue? |
Hi @micaelmalta sorry for the late response! Some things have changed on our end but I am happy to be back on things :) So what you are saying is basically that IF the Unit configuriation is like |
The way it works is that for each application we start a prototype process, this is then used to fork(2) off however many application processes are required. fork(2) (on Linux at least) is a pretty quick operation, say single digit ms, see for example my comment here where I started up 84 PHP application process in short order. Here I start 60 (albeit minimal) Python application processes.
@TheFatal (or anyone else) Could you confirm what OS you are using? Could you also provide a clean unit.log (make sure debugging is OFF) from when starting your application. |
Is it possible to launch python workers simultaneously like uwsgi or gunicorn does ?
In current state when i set for example:
processes: 60
unit starts workers one after another after another etc, so it takes more than 10 minutes for my app
The text was updated successfully, but these errors were encountered: