We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Load testing the standard Python SDK examples for callouts gives CPU saturation under load of 20-30%. There are a few reasons for this:
This limited concurrency leads to gRPC timeouts and other issues under load, despite there being plenty of CPU available. If you instead run the gRPC server under Python multiprocessing library (https://docs.python.org/3/library/multiprocessing.html), as per https://github.com/grpc/grpc/blob/master/examples/python/multiprocessing/server.py, full CPU utilization on a many core processor is possible and the pathologies disappear.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Load testing the standard Python SDK examples for callouts gives CPU saturation under load of 20-30%. There are a few reasons for this:
This limited concurrency leads to gRPC timeouts and other issues under load, despite there being plenty of CPU available. If you instead run the gRPC server under Python multiprocessing library (https://docs.python.org/3/library/multiprocessing.html), as per https://github.com/grpc/grpc/blob/master/examples/python/multiprocessing/server.py, full CPU utilization on a many core processor is possible and the pathologies disappear.
The text was updated successfully, but these errors were encountered: