Bug #66472 | Better MySqlPoolManager IdleCleanUpTimer at startup | ||
---|---|---|---|
Submitted: | 21 Aug 2012 1:40 | Modified: | 3 Jan 2013 0:10 |
Reporter: | Poul Bak | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 6.4.5 | OS: | Any |
Assigned to: | Gabriela Martinez Sanchez | CPU Architecture: | Any |
Tags: | 6.4.5, IdleCleanUpTimer |
[21 Aug 2012 1:40]
Poul Bak
[21 Aug 2012 2:13]
Poul Bak
MySqlPoolManager.cs after change
Attachment: MySqlPoolManager.cs (text/plain), 6.20 KiB.
[21 Aug 2012 3:34]
Poul Bak
The change should be able to go into earlier versions of .Net connector too.
[28 Aug 2012 14:54]
Poul Bak
I should mention that I have run this code for a week now in production.
[5 Oct 2012 21:24]
Gabriela Martinez Sanchez
A fix for this bug has been commited and pushed in the following branches 6.5 and 6.6. To be release in the upcoming versions 6.5.5 and 6.6.3
[3 Jan 2013 0:10]
John Russell
Added to changelog for 6.4.6, 6.5.5, 6.6.4: When an application starts up, creates a connection, and then goes idle after a single database operation, the connections are now cleaned up more quickly: typically after an idle time of 3 minutes rather than 6 minutes. This optimization is especially useful for ASP.net applications on low-traffic sites.