Skip site navigation (1) Skip section navigation (2)

Re: B-Heaps

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Matthew Wakeling <matthew(at)flymine(dot)org>, Eliot Gable <egable+pgsql-performance(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: B-Heaps
Date: 2010-06-20 19:57:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Robert Haas wrote:
> This is drifting a bit off-topic for this thread, but it's not so easy
> to figure out from looking at the TODO which things are actually
> important.  Performance-related improvements are mixed in with
> non-performance related improvements, which are mixed in with things
> that are probably not improvements at all.  And even to the extent
> that you can identify the stuff that's performance-related, it's far
> from obvious which things are most important.  Any thoughts on that

I don't think it's off topic at all actually, and as usually I'll be 
happy to argue why.  Reorganizing the TODO so that it's easier for 
newcomers to consume is certainly a worthwhile but hard to "fund" (find 
time to do relative to more important things) effort itself.  My point 
was more that statistically, *anything* on that list is likely a better 
candidate for something to work on usefully than one of the random 
theoretical performance improvements from research that pop on the lists 
from time to time.  People get excited about these papers and blog posts 
sometimes, but the odds of those actually being in the critical path 
where it represents a solution to a current PostgreSQL bottleneck is 
dramatically lower than that you'll find one reading the list of *known* 
issues.  Want to improve PostgreSQL performance?  Spend more time 
reading the TODO, less looking around elsewhere for problems the 
database may or may not have.

I have a major time sink I'm due to free myself from this week, and the 
idea of providing some guidance for a "low hanging performance fruit" 
section of the TODO is a good one I should take a look at.  I have a 
personal list of that sort already I should probably just make public, 
since the ideas for improving things are not the valuable part I should 
worry about keeping private anyway.

Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support

In response to

pgsql-performance by date

Next:From: Greg SmithDate: 2010-06-20 20:04:09
Subject: Re: Obtaining the exact size of the database.
Previous:From: Jesper KroghDate: 2010-06-20 17:44:29
Subject: Aggressive autovacuuming ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group