title: StackExchange.Redis ConnectionMultiplexer pool for synchronous methods
body: <p>Does implementing a ConnectionMultiplexer pool make sense if we use it for synchronous methods?</p>
  <p>So by pool I mean creating multiple instances of StackExchange.Redis ConnectionMultiplexer, storing those objects and when I want to communicate with Redis server I take the least used one from the pool. This is to prevent timeouts due to large queue size as per No. 10 suggestion in this article: <a href="https://azure.microsoft.com/en-us/blog/investigating-timeout-exceptions-in-stackexchange-redis-for-azure-redis-cache/" rel="nofollow noreferrer">https://azure.microsoft.com/en-us/blog/investigating-timeout-exceptions-in-stackexchange-redis-for-azure-redis-cache/</a></p>
  <p>I'm having doubts because I'm not sure how can a queue even happen if connectionMultiplexer blocks a thread until a call returns.</p>
  <p>It seems to me that having a pool is pointless with sync method calls, but Redis best practice articles suggest creating this kind of pool regardless of method type (sync/async)</p>