Disable Nagle's Algorithm

[bgrainger]

According to https://en.wikipedia.org/wiki/Nagle%27s_algorithm:

In general, since Nagle's algorithm is only a defense against careless applications, it will not benefit a carefully written application that takes proper care of buffering; the algorithm has either no effect, or negative effect on the application.

Since MySqlConnector does buffer writes (it has to know the length of the data that will be transmitted in order to create the MySQL packet header), it seems that Nagle's Algorithm is unnecessary, and possibly harmful.

It may be beneficial to set SocketOptionName.NoDelay on the socket opened by the client, in case the server is using delayed ACKs?

[bgrainger]

Npgsql sets Socket.NoDelay: https://github.com/npgsql/npgsql/blob/368d18d4ebdda6ee8f7f807173a85139840b922e/src/Npgsql/NpgsqlConnector.cs#L906-L907

So does SqlClient: https://github.com/dotnet/SqlClient/blob/83e2c645f0798351b5b7aad944809b5f77cf185c/src/Microsoft.Data.SqlClient/netcore/src/Microsoft/Data/SqlClient/SNI/SNITcpHandle.cs#L225

Connector/NET: https://github.com/mysql/mysql-connector-net/blob/9889a428f1ef9510a5b1a125b51dfd082c1ee72d/MySQL.Data/src/common/MyNetworkStream.cs#L252

[bgrainger]

It may also be useful to turn off delayed ACKs via dotnet/runtime#798 (comment)

Per John Nagle (https://news.ycombinator.com/item?id=10608356):

Short version: set TCP_QUICKACK. If you find a case where that makes things worse, let me know.

[bgrainger]

Fixed in 1.3.0.