multi client session vs single session for multi peer scrappers

[nrbnlulu]

My usecase requires to connect to arbitrary number of devices and each one of them might disconnect at any
point in time.

docs says that

"Unless you are connecting to a large, unknown number of different servers over the lifetime of your application, it is suggested you use a single session for the lifetime of your application to benefit from connection pooling."

1. what is the reason for that?
2. does my usecase fall under this umbrella?
3. would it be different if I use long running websockets?

[Dreamsorcerer]

Well, it can reduce latency when sending multiple requests to the same peer, as the connection can be reused. It can also help to avoid exceeding OS limits on the number of open connections, by limiting the total connections across the session.

[nrbnlulu]

what are you replying to?