[voidlogic]

The most likely cause is in the mysql driver. Go provides an interface for drivers to implement, similar to how JDBC does in Java. One of the go developers, Brad Fitzpatrick, commented [1] that the actual code used by the benchmark looks OK. The discussion of these test results on golang-nuts [1] triggered a number of performance related pull requests [2] to the mysql driver used.

Also of interest: https://code.google.com/p/go/issues/detail?id=5323

1: https://groups.google.com/forum/?fromgroups=#!topic/golang-n...

2: https://github.com/go-sql-driver/mysql/pull/52 https://github.com/go-sql-driver/mysql/pull/55

[JulienSchmidt]

Just for the reference: It was not the drivers fault but an bug in the database/sql package, which was fixed in https://code.google.com/p/go/source/detail?r=45c12efb46

[bhauer]

Thanks for posting the follow up here, Julien. I'm glad this has been fixed. We look forward to the Round 4 numbers with Go fixed up.

[pkroll]

Excellent, thanks much!