Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 29306476435 for ; Tue, 14 Jan 2003 11:09:31 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 6B25F4762EE for ; Tue, 14 Jan 2003 11:04:48 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0EG4r5u016238; Tue, 14 Jan 2003 11:04:53 -0500 (EST) To: captainx0r@yahoo.com Cc: pgsql-performance@postgresql.org Subject: Re: Sun vs. Mac In-reply-to: <20030114154121.53714.qmail@web21103.mail.yahoo.com> References: <20030114154121.53714.qmail@web21103.mail.yahoo.com> Comments: In-reply-to CaptainX0r message dated "Tue, 14 Jan 2003 07:41:21 -0800" Date: Tue, 14 Jan 2003 11:04:52 -0500 Message-ID: <16237.1042560292@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/88 X-Sequence-Number: 735 CaptainX0r writes: > I've read that somewhere (maybe in the archives?) and I got no > change with any of them. But now I'm thinking back - do I need > fsync=true for that to have an affect? I'm not worried about > the cons of having fsync=false at all - and I'm assuming that > should be better than true and open_datasync. You are right that fsync_method is a no-op if you've got fsync turned off. Let me get this straight: the Sun is slower even with fsync off? That shoots down the first theory that I had, which was that the Sun's disk drives were actually honoring fsync while the laptop's drive does not. (See archives for more discussion of that, but briefly: IDE drives are commonly set up to claim write complete as soon as they've absorbed data into their onboard buffers. SCSI drives usually tell the truth about when they've completed a write.) Andrew Sullivan's nearby recommendation to replace qsort() is a good one, but PG 7.3 is already configured to do that by default. (Look in src/Makefile.global to confirm that qsort.o is mentioned in LIBOBJS.) I'd suggest starting with some elementary measurements, for example looking at I/O rates and CPU idle percentage while running the same task on both Solaris and G3. That would at least give us a clue whether I/O or CPU is the bottleneck. regards, tom lane