On Saturday, December 23, 2017 at 9:47:22 PM UTC-8, shashank Jain wrote: > > Reason for the above question was that when we run say 300 threads against > a pool size of 500 connections, we see acquire connection taking upto 20 > secs sometimes across many threads. >
That's a lot of threads for CRuby to handle (JRuby may handle the situation better). If the connections need to be created, I could easily see that kind of performance issue. Preallocating connections may help, but you'll pay a hefty startup penalty in that case. You could try using the mock adapter instead of whatever adapter you are currently using, to see if the performance issue is more related to connection setup vs. connection pool internals. You could also try comparing the current Sequel version to Sequel 4.49.0 and see how much of a difference the connection pool refactoring made. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
