This might be true for SELECTs, but I found INSERTs are massively slower when compared to grouping in transactions.

Which should be obvious. But I could see some reading this blog post and jumping to the wrong conclusion.

It's not the cost of protecting one transaction from another transaction so much as the cost of flushing a transaction to storage to survive a crash.

In the bad old days you had to wait for a lever to move and for the disk to rotate at least once!

▲

hnlmorg 6 hours ago | parent [-]

> It's not the cost of protecting one transaction from another transaction

I know it’s not and never suggested it was.

I was making the point that writes contain more overhead than reads (which should be obvious) so people should bear that in mind when reading this blog post.

Edit: is it “bear” or “bare”? I’m never sure with that phrase haha

	▲	wussboy 2 hours ago \| parent [-]
		It is “bear”, meaning to carry.