Details
-
New Feature
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Updated:
In order to emulate legacy opcode latency with unacknowledged writes, the driver needs to process the database reply asynchronously in a goroutine before returning the connection to the pool.
Originally:
Traditionally, drivers have continued to implement w:0 writes with legacy opcodes to avoid performance regressions. We could skip doing so (as we'd have no previous performance to regress from) and avoid implementing legacy op codes completely which will be unneeded once OP_MSG supports fire and forget writes in 3.8.