pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <pg@rbt.ca>
To: pg@fastcrypt.com
Cc: Frank Wiles <frank@wiles.org>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Low Performance for big hospital server ..
Date: Thu, 06 Jan 2005 12:51:14 -0500
Message-ID: <1105033874.56556.24.camel@home> (raw)
In-Reply-To: <41DD76E5.1090806@fastcrypt.com>
References: <1104831107.41da6283add0c@webmail.moph.go.th>
	<1104939342.41dc094ecb1cf@webmail.moph.go.th>
	<758d5e7f050106041510f07dc5@mail.gmail.com>
	<200501060906.55832.josh@agliodbs.com>
	<20050106111207.52e39d04.frank@wiles.org>
	<41DD76E5.1090806@fastcrypt.com>

On Thu, 2005-01-06 at 12:35 -0500, Dave Cramer wrote:
> Reading can be worse for a normalized db, which is likely what the 
> developers were concerned about.

To a point. Once you have enough data that you start running out of
space in memory then normalization starts to rapidly gain ground again
because it's often smaller in size and won't hit the disk as much.

Moral of the story is don't tune with a smaller database than you expect
to have.

> Frank Wiles wrote:
> 
> >On Thu, 6 Jan 2005 09:06:55 -0800
> >Josh Berkus <josh@agliodbs.com> wrote:
> >
> >  
> >
> >>I can't tell you how many times I've seen this sort of thing.   And
> >>the developers always tell me "Well, we denormalized for performance
> >>reasons ... "
> >>    
> >>
> >
> >  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! 
> >
> > ---------------------------------
> >   Frank Wiles <frank@wiles.org>
> >   http://www.wiles.org
> > ---------------------------------
> >
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 3: if posting/reading through Usenet, please send an appropriate
> >      subscribe-nomail command to majordomo@postgresql.org so that your
> >      message can get through to the mailing list cleanly
> >
> >
> >  
> >
> 
-- 




view thread (38+ messages)  latest in thread

Message-ID: <1105033874.56556.24.camel@home>
Permalink:  ../1105033874.56556.24.camel@home/
Also on:    postgresql.org/message-id/1105033874.56556.24.camel@home

 · 

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: pg@rbt.ca, pg@fastcrypt.com, frank@wiles.org, josh@agliodbs.com
  Subject: Re: Low Performance for big hospital server ..
  In-Reply-To: <1105033874.56556.24.camel@home>

* 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