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

Re: How much memory?

From: Ron Peacetree <rjpeace(at)earthlink(dot)net>
To: PostgreSQL <martin(at)portant(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: How much memory?
Date: 2005-10-27 22:39:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
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.


-----Original Message-----
From: PostgreSQL <martin(at)portant(dot)com>
Sent: Oct 27, 2005 3:31 PM
To: pgsql-performance(at)postgresql(dot)org
Subject: [PERFORM] How much memory?

Is there a rule-of-thumb for determining the amount of system memory a 
database requres (other than "all you can afford")? 


pgsql-performance by date

Next:From: Jim C. NasbyDate: 2005-10-27 22:48:56
Subject: Re: What gets cached?
Previous:From: Martin LesserDate: 2005-10-27 22:09:46
Subject: Re: Reasons and drawbacks for unused item pointers

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