X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5916953349 for ; Mon, 18 Apr 2005 19:49:53 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 20537-02 for ; Mon, 18 Apr 2005 22:49:43 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by svr1.postgresql.org (Postfix) with ESMTP id AB8285334B for ; Mon, 18 Apr 2005 19:49:41 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so1623350wri for ; Mon, 18 Apr 2005 15:49:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=b0ocue5LNy3CiL5fTMjy3/7/7Y7OZeWM4QQQgX5bKbOZnBLRq/Rf1zIknguKzkJC0pDV+nPBd7UIWHVG0tE/shmTjie8zjcsbKkAM47KqdGkivNRU5pVsCqi7wm32Wl9gB5Qq79FeZX2KtNXF3JJfl4b+GPCOvAm/2dqM4ZVLUE= Received: by 10.54.69.3 with SMTP id r3mr1820559wra; Mon, 18 Apr 2005 15:49:44 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Mon, 18 Apr 2005 15:49:44 -0700 (PDT) Message-ID: <33c6269f0504181549571e004b@mail.gmail.com> Date: Mon, 18 Apr 2005 18:49:44 -0400 From: Alex Turner Reply-To: Alex Turner To: Bruce Momjian Subject: Re: How to improve db performance with $7K? Cc: Kevin Brown , pgsql-performance@postgresql.org In-Reply-To: <200504182058.j3IKwTG13788@candle.pha.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050414083608.GC19518@filer> <200504182058.j3IKwTG13788@candle.pha.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.277 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/440 X-Sequence-Number: 11837 Does it really matter at which end of the cable the queueing is done (Assuming both ends know as much about drive geometry etc..)? Alex Turner netEconomist On 4/18/05, Bruce Momjian wrote: > Kevin Brown wrote: > > Greg Stark wrote: > > > > > > > I think you're being misled by analyzing the write case. > > > > > > Consider the read case. When a user process requests a block and > > > that read makes its way down to the driver level, the driver can't > > > just put it aside and wait until it's convenient. It has to go ahead > > > and issue the read right away. > > > > Well, strictly speaking it doesn't *have* to. It could delay for a > > couple of milliseconds to see if other requests come in, and then > > issue the read if none do. If there are already other requests being > > fulfilled, then it'll schedule the request in question just like the > > rest. >=20 > The idea with SCSI or any command queuing is that you don't have to wait > for another request to come in --- you can send the request as it > arrives, then if another shows up, you send that too, and the drive > optimizes the grouping at a later time, knowing what the drive is doing, > rather queueing in the kernel. >=20 > -- > 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 19= 073 >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if you= r > joining column's datatypes do not match >