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 E5FB4D1D283 for ; Tue, 3 Feb 2004 13:49:23 +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 25020-06 for ; Tue, 3 Feb 2004 09:49:17 -0400 (AST) Received: from jefftrout.com (h00a0cc4084e5.ne.client2.attbi.com [24.128.241.68]) by svr1.postgresql.org (Postfix) with SMTP id 45FF8D1B83D for ; Tue, 3 Feb 2004 09:49:14 -0400 (AST) Received: (qmail 32015 invoked from network); 3 Feb 2004 13:49:20 -0000 Received: from localhost (HELO squeegit) (threshar@127.0.0.1) by localhost with SMTP; 3 Feb 2004 13:49:20 -0000 Date: Tue, 3 Feb 2004 08:52:03 -0500 From: Jeff To: josh@agliodbs.com Cc: pgsql-advocacy@postgresql.org, pgsql-performance@postgresql.org Subject: Re: [PERFORM] MySQL+InnoDB vs. PostgreSQL test? Message-Id: <20040203085203.5c5f926c.threshar@torgo.978.org> In-Reply-To: <83927B58-55AA-11D8-99C4-000A959D1424@intercation.com> References: <200402020921.12076.josh@agliodbs.com> <83927B58-55AA-11D8-99C4-000A959D1424@intercation.com> X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/15 X-Sequence-Number: 3586 Well, when I prepared my PG presentation I did some testing of MySQL (So I could be justified in calling it lousy :). I used the latest release (4.0.something I think) I was first bitten by my table type being MyISAM when I thought I set the default ot InnoDB. But I decided since my test was going to be read-only MyISAM should be the best possible choice. I loaded up a couple million records and changed my stored procedure into a perl script [I also decided to use this perl script for testing PG to be fair]. For one client mysql simply screamed. Then I decided to see what happens with 20 clients. MySQL clocked in at 650 seconds. During this time the machine was VERY unresponsive. To be fair, that could be Linux, not MySQL. PG (7.3.4) clocked in at 220 seconds. The machine was perfectly fine during the test - nice and responsive. The hardware wasn't much - dual p2-450 running stock RH8. (2x15k 18g scsi drives for the data volume) Then I decided to try the "beloved" InnoDB. Well.. after it sat for a few hours at 100% cpu loading the data I killed it off and gave up on InnoDB.. I am interested in the numbers. Perhaps I'll fire it up again someday and let it finish loading. Remember - you cannot judge mysql by since connection performance - you can't beat it. But just add up the concurrency and watch the cookies tumble -- Jeff Trout http://www.jefftrout.com/ http://www.stuarthamm.net/