X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8B79AD1B480 for ; Sat, 6 Dec 2003 13:19:54 +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 31461-07 for ; Sat, 6 Dec 2003 09:19:26 -0400 (AST) Received: from candle.pha.pa.us (candle.pha.pa.us [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id F403AD1B442 for ; Sat, 6 Dec 2003 09:19:21 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id hB6DJL916645; Sat, 6 Dec 2003 08:19:21 -0500 (EST) From: Bruce Momjian Message-Id: <200312061319.hB6DJL916645@candle.pha.pa.us> Subject: Re: Has anyone run on the new G5 yet In-Reply-To: <1070526289.4666.35.camel@localhost.localdomain> To: Paul Tuckfield Date: Sat, 6 Dec 2003 08:19:21 -0500 (EST) Cc: pgsql-performance@postgresql.org, shannyconsulting@earthlink.net X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/139 X-Sequence-Number: 4999 Paul Tuckfield wrote: > Biggest problem I've had in the past w. linux in general is that it > seems to make poor VM choices under heavy filesystem IO. I don't really > get exactly where it's going wrong , but I've had numerous experiences > on older systems where bursty IO would seem to cause paging on the box > (pageout of pieces of the oracle SGA shared memory) which is a > performance disaseter. It seems to happen even when the shared memory > was sized reasonably below the size of physical ram, presumably because > linux is too aggressive in allocating filesystem cache (?) anyway, it > seems to make decisions based on desire for zippy workstation > performance and gets burned on thruput on database servers. I'm > guessing this may be an issue for you , when doing heavy IO. Thing is, > it'll show like you're IO bound kindof because you're thrashing. This is not surprising. There has always been an issue with dynamic buffer cache systems contending with memory used by processes. It takes a long time to get the balance right, and still there might be cases where it gets things wrong. Isn't there a Linux option to lock shared memory in to RAM? If so, we should document this in our manuals, but right now, there is no mention of it. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073