pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Turner <armtuk@gmail.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Kevin Brown <kevin@sysexperts.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Mon, 18 Apr 2005 18:49:44 -0400
Message-ID: <33c6269f0504181549571e004b@mail.gmail.com> (raw)
In-Reply-To: <200504182058.j3IKwTG13788@candle.pha.pa.us>
References: <20050414083608.GC19518@filer>
	<200504182058.j3IKwTG13788@candle.pha.pa.us>

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 <pgman@candle.pha.pa.us> 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.
> 
> 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.
> 
> --
>   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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
>



view thread (119+ messages)  latest in thread

Message-ID: <33c6269f0504181549571e004b@mail.gmail.com>
Permalink:  ../33c6269f0504181549571e004b@mail.gmail.com/
Also on:    postgresql.org/message-id/33c6269f0504181549571e004b@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: armtuk@gmail.com, pgman@candle.pha.pa.us, kevin@sysexperts.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <33c6269f0504181549571e004b@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox