Next up in the "quick look" series is a discussion of connection
management best practices and the memory usage implications of
idle connections in Aurora and MySQL. I'll also throw in some
notes on how to configure your connection pools to avoid
unpleasant surprises.
Thread handling in Aurora vs MySQL Community MySQL
editions use "one-thread-per-connection" approach to thread
handling. It means that each individual user connection receives
a dedicated OS thread within the mysqld process. This comes with
issues, such as:
- Relatively high memory usage with large number of user connections, even if the connections are completely idle.
- Higher internal server contention and context switching overhead when working with thousands of user connections.
To avoid such issues, some servers support a thread pool
approach. Examples include Percona Server and Amazon
Aurora.
…