Peter Eisentraut <peter_e@xxxxxxx> writes:
> On a particular system, loading 1 million rows (100 bytes, nothing
> fancy) into PostgreSQL one transaction at a time takes about 90
> minutes. Doing the same in MySQL/InnoDB takes about 3 minutes.
What sort of hardware, exactly?
Simple division says that that's about 11K transactions per minute,
which is more or less what you could expect to get with a 15000RPM
drive if everyone is honest and a commit actually involves bits hitting
a platter. Now we've talked about schemes for committing more than one
transaction per disk revolution, but there's no way we could get to 30
per revolution given our lack of knowledge about the actual disk layout.
I don't think I believe that InnoDB is really truly committing 330K
transactions per minute. Suggest that the customer try a pull-the-plug
type of test. Does the DB come back at all, and if so how close to the
last reported-committed row has it got?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
