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 38FFA52D42 for ; Wed, 20 Apr 2005 15:50:10 -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 08114-08 for ; Wed, 20 Apr 2005 18:50:04 +0000 (GMT) Received: from wproxy.gmail.com (unknown [64.233.184.194]) by svr1.postgresql.org (Postfix) with ESMTP id 9707F53DB4 for ; Wed, 20 Apr 2005 14:12:09 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so219401wri for ; Wed, 20 Apr 2005 10:10:49 -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=BFCFuDNA6oMzHluyVf+1KhewIHQ4X3Dda33B71wt+0ZeTa1Lx3gl+wrG4ML9HejF81XCwqCM7BYC6qYyJTRwvf5g+bi1EnFNpz84JcQSDsVCOEt0X94tjx7kOr8okBXhB67g5qMYduFxYuVBKJ2ZmeX034W/O74vnY51eyEGx5I= Received: by 10.54.16.28 with SMTP id 28mr115062wrp; Wed, 20 Apr 2005 10:04:06 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Wed, 20 Apr 2005 10:04:04 -0700 (PDT) Message-ID: <33c6269f050420100455955060@mail.gmail.com> Date: Wed, 20 Apr 2005 13:04:04 -0400 From: Alex Turner Reply-To: Alex Turner To: Dave Held Subject: Re: How to improve db performance with $7K? Cc: pgsql-performance@postgresql.org In-Reply-To: <49E94D0CFCD4DB43AFBA928DDD20C8F9026184BB@asg002.asg.local> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <49E94D0CFCD4DB43AFBA928DDD20C8F9026184BB@asg002.asg.local> 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/522 X-Sequence-Number: 11919 Whilst I admire your purist approach, I would say that if it is beneficial to performance that a kernel understand drive geometry, then it is worth investigating teaching it how to deal with that! I was less referrring to the kernel as I was to the controller. Lets say we invented a new protocol that including the drive telling the controller how it was layed out at initialization time so that the controller could make better decisions about re-ordering seeks. It would be more cost effective to have that set of electronics just once in the controller, than 8 times on each drive in an array, which would yield better performance to cost ratio. Therefore I would suggest it is something that should be investigated. After all, why implemented TCQ on each drive, if it can be handled more effeciently at the other end by the controller for less money?! Alex Turner netEconomist On 4/19/05, Dave Held wrote: > > -----Original Message----- > > From: Alex Turner [mailto:armtuk@gmail.com] > > Sent: Monday, April 18, 2005 5:50 PM > > To: Bruce Momjian > > Cc: Kevin Brown; pgsql-performance@postgresql.org > > Subject: Re: [PERFORM] How to improve db performance with $7K? > > > > Does it really matter at which end of the cable the queueing is done > > (Assuming both ends know as much about drive geometry etc..)? > > [...] >=20 > The parenthetical is an assumption I'd rather not make. If my > performance depends on my kernel knowing how my drive is laid > out, I would always be wondering if a new drive is going to > break any of the kernel's geometry assumptions. Drive geometry > doesn't seem like a kernel's business any more than a kernel > should be able to decode the ccd signal of an optical mouse. > The kernel should queue requests at a level of abstraction that > doesn't depend on intimate knowledge of drive geometry, and the > drive should queue requests on the concrete level where geometry > matters. A drive shouldn't guess whether a process is trying to > read a file sequentially, and a kernel shouldn't guess whether > sector 30 is contiguous with sector 31 or not. >=20 > __ > David B. Held > Software Engineer/Array Services Group > 200 14th Ave. East, Sartell, MN 56377 > 320.534.3637 320.253.7800 800.752.8129 >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings >