pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: justin <justin@emproshunts.com>
To: pgsql-performance@postgresql.org
Subject: Re: Need help with 8.4 Performance Testing
Date: Tue, 09 Dec 2008 18:19:35 -0500
Message-ID: <493EFD07.4080201@emproshunts.com> (raw)
In-Reply-To: <22285.1228862315@sss.pgh.pa.us>
References: <C5642B9E.F8A%scott@richrelevance.com>
	<22285.1228862315@sss.pgh.pa.us>

Tom Lane wrote:
> Scott Carey <scott@richrelevance.com> writes:
>   
>> Which brings this back around to the point I care the most about:
>> I/O per second will diminish as the most common database performance limiting factor in Postgres 8.4's lifetime, and become almost irrelevant in 8.5's.
>> Becoming more CPU efficient will become very important, and for some, already is.  The community needs to be proactive on this front.
>> This turns a lot of old assumptions on their head, from the database down through the OS and filesystem.  We're bound to run into many surprises due to this major shift in something that has had its performance characteristics taken for granted for decades.
>>     
>
> Hmm ... I wonder whether this means that the current work on
> parallelizing I/O (the posix_fadvise patch in particular) is a dead
> end.  Because what that is basically going to do is expend more CPU
> to improve I/O efficiency.  If you believe this thesis then that's
> not the road we want to go down.
>
> 			regards, tom lane
>   

What does the CPU/ Memory/Bus performance road map look like?

Is the IO performance for storage device for what ever it be, going to 
be on par with the above to cause this problem?

Once IO performance numbers start jumping up I think DBA will have the 
temptation start leaving more and more data in the production database  
instead of moving it out of the production database. Or start 
consolidating databases onto fewer servers .  Again pushing more load 
onto the IO. 

view thread (56+ messages)  latest in thread

Message-ID: <493EFD07.4080201@emproshunts.com>
Permalink:  ../493EFD07.4080201@emproshunts.com/
Also on:    postgresql.org/message-id/493EFD07.4080201@emproshunts.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: justin@emproshunts.com
  Subject: Re: Need help with 8.4 Performance Testing
  In-Reply-To: <493EFD07.4080201@emproshunts.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