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.

Sign up for GitHub

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

Concurrency level is not handled properly #32

Open

alexeykudinkin opened this issue Jan 26, 2024 · 0 comments

alexeykudinkin commented Jan 26, 2024

Currently, library makes it look as if it can support arbitrary concurrency levels, but in reality it actually doesn't:

Each actor require 1 CPU (ie number of actual concurrent workers will be limited by the number of CPUs in your Ray cluster)
We're not asserting number of actors produced (ie if Ray can't schedule all of them, user will never know)
Tasks to query the target endpoint are spun up from a single loop, therefore bound by the performance of submitting tasks to Ray from a single loop

alexeykudinkin assigned alexeykudinkin and avnishn and unassigned alexeykudinkin and avnishn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment