Ray is a unified framework for scaling AI and Python applications. Ray consists of a core distributed runtime and a set of AI Libraries for accelerating ML workloads.
Based on the recent investigation, it seems like each of ray workers has 8~9 direct connections to Redis along with other connections to other components. We should refactor code to use a shared pool among processes.
Reproduction (REQUIRED)
Please provide a script that can be run to reproduce the issue. The script should have no external library dependencies (i.e., use fake or mock data / environments):
Run a ray cluster. Create a new actor and check the number of redis connection using redis-cli -p 6379 -a [password] client list | wc -l
[ ] I have verified my script runs in a clean environment and reproduces the issue.
[ ] I have verified the issue also occurs with the latest wheels.
What is the problem?
Based on the recent investigation, it seems like each of ray workers has 8~9 direct connections to Redis along with other connections to other components. We should refactor code to use a shared pool among processes.
Reproduction (REQUIRED)
Please provide a script that can be run to reproduce the issue. The script should have no external library dependencies (i.e., use fake or mock data / environments):
Run a ray cluster. Create a new actor and check the number of redis connection using
redis-cli -p 6379 -a [password] client list | wc -l