Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0LDX8V25829 for ; Mon, 21 Jan 2002 08:33:08 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g0LDX4422570; Mon, 21 Jan 2002 08:33:04 -0500 (EST) From: Bruce Momjian Message-Id: <200201211333.g0LDX4422570@candle.pha.pa.us> Subject: Re: Performance In-Reply-To: <3C4BE7C5.20198.1107D7@localhost> To: mark@vestnesis.lv Date: Mon, 21 Jan 2002 08:33:04 -0500 (EST) CC: pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL96 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200201/130 X-Sequence-Number: 3017 See techdocs performance article: http://techdocs.postgresql.org Martins Zarins wrote: > On 18 Jan 2002, at 9:22, Jeremy Buchmann wrote: > > > > It's more than just processor cache, it's your whole I/O subsystem. > > How fast are your drives? How fast is the drive controller? How much > > cache is on each drive? How much cache is on the drive controller? > > Are you going to use a RAID? If so, what type? Do you have enough > > memory for the size of the database and type of queries you're going > > to run? > Is there any good doc about this on net? > (About disc cache, raid cache processor cache and queries - how > they influence each other?) > > Mark > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026