What limits Postgres performance when the whole database lives in cache? - Mailing list pgsql-general

From dandl
Subject What limits Postgres performance when the whole database lives in cache?
Date
Msg-id 000e01d20507$a5bafa10$f130ee30$@andl.org
Whole thread Raw
Responses Re: What limits Postgres performance when the whole database lives in cache?  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-general

Re this talk given by Michael Stonebraker:

http://slideshot.epfl.ch/play/suri_stonebraker

 

He makes the claim that in a modern ‘big iron’ RDBMS such as Oracle, DB2, MS SQL Server, Postgres, given enough memory that the entire database lives in cache, the server will spend 96% of its memory cycles on unproductive overhead. This includes buffer management, locking, latching (thread/CPU conflicts) and recovery (including log file reads and writes).

 

[Enough memory in this case assumes that for just about any business, 1TB is enough. The intent of his argument is that a server designed correctly for it would run 25x faster.]

 

I wondered if there are any figures or measurements on Postgres performance in this ‘enough memory’ environment to support or contest this point of view?

 

Regards

David M Bennett FACS


Andl - A New Database Language - andl.org

 

pgsql-general by date:

Previous
From: Patrick B
Date:
Subject: Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2
Next
From: Jonas Tehler
Date:
Subject: Duplicate data despite unique constraint