[core] Make number of connections and thread number of object manager…

… client tunable. (ray-project#41421)

The number of connections will impact the transfer performance. Make it tunable for now so that the user can just increase it on demands.

src/ray/common/ray_config_def.h

@@ -886,3 +886,14 @@ RAY_CONFIG(bool, enable_autoscaler_v2, false)
 // Python GCS client number of reconnection retry and timeout.
 RAY_CONFIG(int64_t, nums_py_gcs_reconnect_retry, 5)
 RAY_CONFIG(int64_t, py_gcs_connect_timeout_s, 30)
+
+// The number of sockets between object manager.
+// The higher the number the higher throughput of the data
+// trasfer it'll be, but it'll also user more sockets and
+// more CPU resources.
+RAY_CONFIG(int, object_manager_client_connection_num, 4)
+
+// The number of object manager thread. By default, it's
+// std::min(std::max(2, num_cpus / 4), 8)
+// Update this to overwrite it.
+RAY_CONFIG(int, object_manager_rpc_threads_num, 0)

src/ray/raylet/main.cc

@@ -304,6 +304,10 @@ int main(int argc, char *argv[]) {
 
  object_manager_config.rpc_service_threads_number =
  std::min(std::max(2, num_cpus / 4), 8);
+ if (RayConfig::instance().object_manager_rpc_threads_num() != 0) {
+ object_manager_config.rpc_service_threads_number =
+ RayConfig::instance().object_manager_rpc_threads_num();
+ }
  object_manager_config.object_chunk_size =
  RayConfig::instance().object_manager_default_chunk_size();
 

src/ray/rpc/object_manager/object_manager_client.h

@@ -40,7 +40,8 @@ class ObjectManagerClient {
  ObjectManagerClient(const std::string &address,
  const int port,
  ClientCallManager &client_call_manager,
- int num_connections = 4)
+ int num_connections =
+ ::RayConfig::instance().object_manager_client_connection_num())
  : num_connections_(num_connections) {
  push_rr_index_ = rand() % num_connections_;
  pull_rr_index_ = rand() % num_connections_;