X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5636F3A41E1 for ; Thu, 6 Jan 2005 17:53:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 28195-07 for ; Thu, 6 Jan 2005 17:52:51 +0000 (GMT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id BEF943A460E for ; Thu, 6 Jan 2005 17:52:45 +0000 (GMT) Received: from dyn-68-143.tor.dsl.tht.net (dyn-68-143.tor.dsl.tht.net [134.22.68.143]) by tht.net (Postfix) with ESMTP id 97CF476A28; Thu, 6 Jan 2005 12:52:47 -0500 (EST) Subject: Re: Low Performance for big hospital server .. From: Rod Taylor To: pg@fastcrypt.com Cc: Frank Wiles , Josh Berkus , Postgresql Performance 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> Content-Type: text/plain Date: Thu, 06 Jan 2005 12:51:14 -0500 Message-Id: <1105033874.56556.24.camel@home> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/72 X-Sequence-Number: 9762 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 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 > > 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 > > > > > > > > > --