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

Re: How much memory?

From: Alex Turner <armtuk(at)gmail(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Ron Peacetree <rjpeace(at)earthlink(dot)net>,PostgreSQL <martin(at)portant(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: How much memory?
Date: 2005-10-28 14:02:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Reasons not to buy from Sun or Compaq - why get Opteron 252 when a 240
will do just fine for a fraction of the cost, which of course they
don't stock, white box all the way baby ;).  My box from Sun or Compaq
or IBM is 2x the whitebox cost because you can't buy apples to apples.
 We have a bitchin' DB server for $7.5k


On 10/27/05, Jim C. Nasby <jnasby(at)pervasive(dot)com> wrote:
> On Thu, Oct 27, 2005 at 06:39:33PM -0400, Ron Peacetree wrote:
> > Databases basically come in 4 sizes:
> >
> > 1= The entire DB fits into memory.
> > 2= The performance critical table(s) fit(s) into memory
> > 3= The indexes of the performance critical table(s) fit into memory.
> > 4= Neither the performance critical tables nor their indexes fit into memory.
> >
> > Performance decreases (exponentially), and development + maintenance cost/difficulty/pain increases (exponentially), as you go down the list.
> >
> > While it is often not possible to be in class "1" above, do everything you can to be in at least class "3" and do everything you can to avoid class "4".
> >
> > At ~$75-$150 per GB as of this post, RAM is the cheapest investment you can make in a high perfomance, low hassle DBMS.  IWill's and Tyan's 16 DIMM slot mainboards are worth every penny.
> And note that your next investment after RAM should be better disk IO.
> More CPUs *generally* don't buy you much (if anything). My rule of
> thumb: the only time your database should be CPU-bound is if you've got
> a bad design*.
> *NOTE: before everyone goes off about query parallelism and big
> in-memory sorts and what-not, keep in mind I said "rule of thumb". :)
> --
> Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
> Pervasive Software    work: 512-231-6117
> vcard:       cell: 512-569-9461
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

In response to

pgsql-performance by date

Next:From: Csaba NagyDate: 2005-10-28 15:14:21
Subject: How long it takes to vacuum a big table
Previous:From: Nick HowdenDate: 2005-10-28 12:22:44

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