Bug #60366 | Calling stored procedure with output parameters may hugely decrease performance | ||
---|---|---|---|
Submitted: | 7 Mar 2011 10:43 | Modified: | 4 May 2011 14:25 |
Reporter: | Pavel Bazanov | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 6.3.5, 6.3.6 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | OUT, Output, Parameters, params, performance, slow, SP, stored procedures |
[7 Mar 2011 10:43]
Pavel Bazanov
[7 Mar 2011 10:44]
Pavel Bazanov
fixed the category.
[7 Mar 2011 10:48]
Pavel Bazanov
PS. I took the code in the How to repeat section from the test with dotConnect. It uses MySqlType enumeration. For testing with MySqlConnector.NET you just need to change it to DbType enumeration.
[12 Mar 2011 9:06]
Pavel Bazanov
Someone please take a look at this issue.
[17 Mar 2011 22:53]
Pavel Bazanov
I think this is serious, I can't use stored procedures with output parameters in performance critical areas because of this problem :(
[8 Apr 2011 22:38]
Pavel Bazanov
up
[4 May 2011 14:25]
Reggie Burnett
Fixed in 6.3.7, 6.4.1+
[7 May 2011 16:24]
Paul DuBois
Noted in 6.3.7, 6.4.1 changelogs. Calling a stored procedure with output parameters caused a marked performance decrease. CHANGESET - http://lists.mysql.com/commits/136669