X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9DA9FD1D7BE for ; Tue, 3 Feb 2004 17:03:36 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 16757-07 for ; Tue, 3 Feb 2004 13:03:32 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 3BB0DD1D342 for ; Tue, 3 Feb 2004 13:03:30 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i13H3BfA019419; Tue, 3 Feb 2004 12:03:12 -0500 (EST) To: Jeff Cc: rigmor.ukuhe@finestmedia.com, josh@agliodbs.com, pgsql-advocacy@postgresql.org, pgsql-performance@postgresql.org Subject: Re: [PERFORM] MySQL+InnoDB vs. PostgreSQL test? In-reply-to: <20040203115502.51820b31.threshar@torgo.978.org> References: <20040203085203.5c5f926c.threshar@torgo.978.org> <20040203105349.2f700477.threshar@torgo.978.org> <19175.1075826765@sss.pgh.pa.us> <20040203115502.51820b31.threshar@torgo.978.org> Comments: In-reply-to Jeff message dated "Tue, 03 Feb 2004 11:55:02 -0500" Date: Tue, 03 Feb 2004 12:03:11 -0500 Message-ID: <19418.1075827791@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/25 X-Sequence-Number: 3596 Jeff writes: > On Tue, 03 Feb 2004 11:46:05 -0500 > Tom Lane wrote: >> I did some idle, very unscientific tests the other day that indicated >> that MySQL insert performance starts to suck with just 2 concurrent >> inserters. Given a file containing 10000 INSERT commands, a single >> mysql client ran the file in about a second. So if I feed the file >> simultaneously to two mysqls in two shell windows, it should take >> about two seconds total to do the 20000 inserts, right? The observed >> times were 13 to 15 seconds. (I believe this is with a MyISAM table, >> since I just said CREATE TABLE without any options.) > MyISAM is well known to suck if you update/insert/delete because it > simply aquires a full table lock when you perform those operations! Sure, I wasn't expecting it to actually overlap any operations. (If you try the same test with Postgres, the scaling factor is a little better than linear because we do get some overlap.) But that shouldn't result in a factor-of-seven slowdown. There's something badly wrong with their low-level locking algorithms I think. regards, tom lane