pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Frank Wiles <frank@wiles.org>
Subject: Re: Denormalization WAS: Low Performance for big hospital server ..
Date: Thu, 6 Jan 2005 09:38:45 -0800
Message-ID: <200501060938.45688.josh@agliodbs.com> (raw)
In-Reply-To: <20050106111207.52e39d04.frank@wiles.org>
References: <1104831107.41da6283add0c@webmail.moph.go.th>
	<200501060906.55832.josh@agliodbs.com>
	<20050106111207.52e39d04.frank@wiles.org>

Frank,

>   Now that's rich.  I don't think I've ever seen a database perform
>   worse after it was normalized.  In fact, I can't even think of a
>   situation where it could!

Oh, there are some.    For example, Primer's issues around his dating 
database; it turned out that a fully normalized design resulted in very bad 
select performance because of the number of joins involved.  Of course, the 
method that did perform well was *not* a simple denormalization, either.

The issue with denormalization is, I think, that a lot of developers cut their 
teeth on the likes of MS Access, Sybase 2 or Informix 1.0, where a 
poor-performing join often didn't complete at all.   As a result, they got 
into the habit of "preemptive tuning"; that is, doing things "for performance 
reasons" when the system was still in the design phase, before they even know 
what the performance issues *were*.     

Not that this was a good practice even then, but the average software project 
allocates grossly inadequate time for testing, so you can see how it became a 
bad habit.  And most younger DBAs learn their skills on the job from the 
older DBAs, so the misinformation gets passed down.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (2+ messages)  latest in thread

Message-ID: <200501060938.45688.josh@agliodbs.com>
Permalink:  ../200501060938.45688.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200501060938.45688.josh@agliodbs.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: josh@agliodbs.com, frank@wiles.org
  Subject: Re: Denormalization WAS: Low Performance for big hospital server ..
  In-Reply-To: <200501060938.45688.josh@agliodbs.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