4 ms·
The biggest performance hit right now is getting the data into MySQL (the network stack). We're inserting one row at a time, so most of the time is spent on the
by coffeemug 17y ago
The biggest performance hit right now is getting the data into MySQL (the network stack). We're inserting one row at a time, so most of the time is spent on the wire. Effectively, it's a different benchmark.
BTW, an average drive rotates at 250 revolutions per second. If you flush on every transaction, this is roughly how many transactions you'll be able to sustain. Anything more than that, and you have to batch transactions in memory.
- Maro 17y agoSo it's one network roundtrip + commit per INSERT?
- coffeemug 17y agoYes, that's correct. The benchmark was run on localhost, so it might be going through loopback, but most of the time is spent in the network stack.
- Maro 17y agoInteresting! Is there a theoretical maximum throughput that can be estimated based on the parameters of the SSD (and other variables)?
- rarrrrrr 17y agoAny difference connecting through a local unix domain socket instead of localhost (to avoid TCP overhead?)
- leif 17y agoWe'll be looking at many ways to cut networking overhead over the coming weeks, including socket communication (though I don't know if MySQL supports this).
- akirk 17y agoSorry for being picky, but don't "average drives" rotate between 5400 rpm (rotations per minute == 90 rotations per sec) and 7200 rpm (== 120 rotations per second)?