pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Brown <kevin@sysexperts.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Fri, 15 Apr 2005 01:28:54 -0400
Message-ID: <29785.1113542934@sss.pgh.pa.us> (raw)
In-Reply-To: <20050415050336.GE19518@filer>
References: <20050406224102.GM93835@decibel.org>
	<33c6269f0504061732195f6ae4@mail.gmail.com>
	<87wtrfmgt5.fsf@stark.xeocode.com>
	<13449.1112847297@sss.pgh.pa.us>
	<20050414055655.GB19518@filer>
	<878y3lj23o.fsf@stark.xeocode.com>
	<20050414083608.GC19518@filer>
	<446.1113489854@sss.pgh.pa.us>
	<20050415020337.GD19518@filer>
	<28523.1113532916@sss.pgh.pa.us>
	<20050415050336.GE19518@filer>

Kevin Brown <kevin@sysexperts.com> writes:
> In the case of pure random reads, you'll end up having to wait an
> average of half of a rotation before beginning the read.

You're assuming the conclusion.  The above is true if the disk is handed
one request at a time by a kernel that doesn't have any low-level timing
information.  If there are multiple random requests on the same track,
the drive has an opportunity to do better than that --- if it's got all
the requests in hand.

			regards, tom lane



view thread (119+ messages)  latest in thread

Message-ID: <29785.1113542934@sss.pgh.pa.us>
Permalink:  ../29785.1113542934@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29785.1113542934@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, kevin@sysexperts.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <29785.1113542934@sss.pgh.pa.us>

* 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