pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PFC <lists@boutiquenumerique.com>
To: Kevin Brown <kevin@sysexperts.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Fri, 15 Apr 2005 12:07:43 +0200
Message-ID: <op.so9qe5y2th1vuj@localhost> (raw)
In-Reply-To: <33c6269f050406151241b01148@mail.gmail.com>
References: <d31f71$2epm$1@news.hub.org>
	<33c6269f050406151241b01148@mail.gmail.com>
	<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>



> My argument is that a sufficiently smart kernel scheduler *should*
> yield performance results that are reasonably close to what you can
> get with that feature.  Perhaps not quite as good, but reasonably
> close.  It shouldn't be an orders-of-magnitude type difference.

	And a controller card (or drive) has a lot less RAM to use as a cache /  
queue for reordering stuff than the OS has, potentially the OS can us most  
of the available RAM, which can be gigabytes on a big server, whereas in  
the drive there are at most a few tens of megabytes...

	However all this is a bit looking at the problem through the wrong end.  
The OS should provide a multi-read call for the applications to pass a  
list of blocks they'll need, then reorder them and read them the fastest  
possible way, clustering them with similar requests from other threads.

	Right now when a thread/process issues a read() it will block until the  
block is delivered to this thread. The OS does not know if this thread  
will then need the next block (which can be had very cheaply if you know  
ahead of time you'll need it) or not. Thus it must make guesses, read  
ahead (sometimes), etc...



view thread (119+ messages)  latest in thread

Message-ID: <op.so9qe5y2th1vuj@localhost>
Permalink:  ../op.so9qe5y2th1vuj@localhost/
Also on:    postgresql.org/message-id/op.so9qe5y2th1vuj@localhost

 · 

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: lists@boutiquenumerique.com, kevin@sysexperts.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <op.so9qe5y2th1vuj@localhost>

* 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