For the RPC Framework it seems like this is happening since Gloo creates a tcp connection for all combination of processes in the group.
I’m wondering if this can be avoid in TensorPipe where the TCP connections are created on demand and kept in a pool for reuse. Typically in a RPC environment, we’re not talking to all the nodes in the group at the same time.
@yueyilia Could you add some details about your use case for RPC here? Are all the nodes (1024) communicating with all the other nodes in your application at the same time? Is it possible to run 1 process per server in your application to get around this in the short term? If GIL is  currently the bottleneck, there is some amount of TorchScript support in the RPC framework that might help getting round GIL.