> My question is why does the db not re-using the connections or why does it not release the connections soon enough?
Because number of required connections are very volatile than you think. When required connections changed like 50 -> 0 -> 50 -> 0 -> 50 -> 0 in each 50ms (300ms total), you closes 90 connections in 300ms! And there are some lag between "closing" connection and "connection is closed". That's why "Too many connections" happens when connections are opened and closed very quickly. I recommend to use db.SetMaxOpenConns(50) db.SetMaxIdleConns(50) db.SetMaxConnLifetime(time.Second * 10) 10sec is long enough for LAN (~10ms RTT, DNS is quick). But if RTT of DB server is very long or DNS is very slow, longer lifetime may increase performance significantly. On the other hand, please note longer lifetime may increase possibility of some trobule. (e.g. network error, slower failover, etc...) -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
