Every day, DPA shows that the Top SQL in my MySQL (Community 5.6.27, Windows Server 2012) is a solo "COMMIT" statement.


This is not very helpful in drilling down to find bottlenecks or poor-performing SQL code. Is this a factor of how MySQL is parsed, a side-effect of how the code is constructed in our environment, or just the way that DPA sees and reports on the engine's performance and behavior? Is there some way within DPA to connect this "query" to the transaction that is being committed? I want to use this tool to improve my code (and server performance), but I'm not getting any useful information at this point.