-
Notifications
You must be signed in to change notification settings - Fork 153
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
When aiotools num_worker set as many as cpu cores, dead with error. #17
Comments
I'll look into it! |
The number of workers in the Backend.AI gateway is not related to the performance of your Backend.AI user-code execution. It mainly affects the API (HTTP request) processing throughput. Therefere it is safe to have low numbers for private setups where the concurrent client connections are far less than hundreds or thousands. Even a single thread setup can handle hundreds of concurrent HTTP requests without hassles. (In Backend.AI, the main performance-limiting factor is the latency of Docker APIs in the agents.) So I'm going to add a patch so that you can customize the number of gateway processes using a CLI argument while its default is set to a small number (at most 4). |
As there are no more responses after I have provided the patch, closing the issue. |
If I specify num_worker as the number of cores as mentioned in the title, an error occurs.
So I specify 20 worker. any other way to solve this?
The text was updated successfully, but these errors were encountered: