Bradley Grainger

> It does add some increased risk that unusual SQL will be transformed/truncated by this new code and thus introduce new bugs. Indeed, the ADO.NET conformance tests found a problem:...

There is not currently any such method. Do you know of another ADO.NET provider that exposes similar metrics? (Just curious if there's an existing example of exposing such an API.)

I am looking for guidance (from the ADO.NET or ASP.NET Core team) about high-performance instrumentation with EventSource or DiagnosticSource (#471). One can also imagine exposing Prometheus-style metrics or integrating with...

https://github.com/mysql-net/MySqlConnector/issues/1137 provides a link to [SQL Server Provider Statistics](https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql/provider-statistics-for-sql-server), which is an in-memory (?) Dictionary enabled via a connection-string setting. This could provide a template for a low-overhead approach, but...

Thanks for the detailed writeup. My first thought is that using async I/O in MySqlConnector could be contributing to the discrepancy (by allowing greater parallelism and throughput). (MySql.Data [doesn't support...

You could also add `;DeferConnectionReset=true` to MySqlConnector, as that will eliminate background connection resetting work that reduces latency, but can result in higher concurrent database session usage. (Both these suggestions...

Also note that MySql.Data doesn't reset the connection state when `MySqlConnection.Open(Async)` is called, but MySqlConnector does. For a fair comparison, add `;ConnectionReset=true` (recommended) or `;ConnectionReset=false` to both connection strings.

> I ran a load test that simulate 1K http requests / second What is the maximum number of simultaneous HTTP connections your load test reaches? If it's 1000 at...

> The pool didn't reach the connection limit this time and I didn't see errors I've found an issue with `DeferConnectionReset=false` (the default) that can increase the total number of...

@huraken Can you try your original scenario (with the original connection string) again with MySqlConnector 1.3.8? I'm hoping to see some significant improvements.