Re: Hardware/OS recommendations for large databases ( - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: Hardware/OS recommendations for large databases (
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB3417DD907@Herge.rcsinc.local
Whole thread Raw
List pgsql-performance
> Remember - large DB is going to be IO bound.  Memory will get thrashed
> for file block buffers, even if you have large amounts, it's all gonna
> be cycled in and out again.

'fraid I have to disagree here. I manage ERP systems for manufacturing
companies of various sizes.  My systems are all completely cpu
bound...even though the larger database are well into two digit gigabyte
sizes, the data turnover while huge is relatively constrained and well
served by the O/S cache. OTOH, query latency is a *huge* factor and we
do everything possible to lower it.  Even if the cpu is not 100% loaded,
faster processors make the application 'feel' faster to the client.

Merlin



pgsql-performance by date:

Previous
From: Alex Turner
Date:
Subject: Re: Hardware/OS recommendations for large databases (
Next
From: David Boreham
Date:
Subject: Re: Hardware/OS recommendations for large databases (