PoolSize Question

[pthargis]

@imperugo and others - I am new to this library. What is the purpose of the PoolSize? Does it create multiple ConnectionMultiplexer or multiple connections inside the ConnectionMultiplexer?

[imperugo]

Exactly. It create multiple connections and use the less loaded in order to reduce the possible number of timeouts during high stress requests.

[pthargis]

@imperugo - Thanks for your replay. What we found while testing the library, ConnectionMultiplexer does not close the existing connections if we refresh the client due to configuration changes such as Password, which leads to a connection leak? Can you recommend how we can take it forward?

[imperugo]

This because the connection is registered as singleton for performance reason (the connection is the most expensive part).
You have to restart the application in order to apply the changes or I've to offer the opportunity to re-initialise the pool but this could've be complicated / cause lock during multiple concurrent requests.

Last, but not least, you can swap my Connection Pool Manager with your own logic thanks to the DI.

[pthargis]

@imperugo - 1. can you provide a link or an example of swapping (thread conversation) my Connection Pool Manager?
2. Can we use the dispose method to dispose of the existing connection alone?