5

I find it hard to create a connection pool in Redis with 300+ connections. I am about use it in a volatile environment in a multi-threaded app. Is anyone experienced with a deployment like this that could help me determine if this is possible? Thanks.

L0j1k
  • 12,255
  • 7
  • 53
  • 65
itsraja
  • 1,640
  • 4
  • 32
  • 48
  • the question is why do you need to keep all this connections actives at the same time ? Better to close connexion once job performed and not to leave them running. Keep your architecture simple will prevent bugs. – jeorfevre Jun 12 '17 at 12:28

1 Answers1

5

You shouldn't have any issues on the redis side - http://jaksprats.wordpress.com/2010/09/22/12/ shows performance data for up to 64k concurrent connections.

300 is a long way from 64k, but it is a lot closer to the maximum number of threads java can reasonably handle. That varies depending on the hardware you are using, JVM settings, and how much each thread is doing. There isn't enough information in your question to know for sure, but most likely this is where you are running into problems.

Tom Clarkson
  • 16,074
  • 2
  • 43
  • 51