pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Smith <greg@2ndquadrant.com>
To: Benjamin Krajmalnik <kraj@servoyant.com>
Cc: Keith Gabryelski <keith@fluentmobile.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: how do you manage postgres 9's postgres process's memory
Date: Sun, 13 Feb 2011 22:05:32 -0500
Message-ID: <4D589BFC.5040608@2ndquadrant.com> (raw)
In-Reply-To: <F4E6A2751A2823418A21D4A160B689887B0EE9@fletch.stackdump.local>
References: <AANLkTi=c69joHpUj=rHm6irgy-UfCF6Nmeb4nBSWNp-N@mail.gmail.com>
	<4D579CEE020000250003A936@gw.wicourts.gov>
	<AANLkTi=5CshYJVJ=FUAtR6=xTk1L8nk0roZCtLmZ4WSR@mail.gmail.com>
	<F4E6A2751A2823418A21D4A160B689887B0EE9@fletch.stackdump.local>

Benjamin Krajmalnik wrote:
>
> I ordered some massive servers, and in the course of benchmarking them 
> following their instructions it exposed apparent hardware issues -- so 
> the 2 massive servers as well as one of the smaller ones got shipped 
> back to the supplier for them to check it out.  Had I assumed the 
> servers were performing as the specs on paper indicated, I would have 
> been in serious trouble a few months down the line as we would have 
> reached limitations we were not aware of.
>

As a general statistic on this topic, about 1 out of every 3 servers I 
come across has a serious problem of this sort.  Maybe half of those are 
just software misconfiguration that can be fixed before deployment, the 
rest are more serious issues.  Nobody should every trust their hardware 
vendors to get things right, everyone's production schedules are just 
too tight nowadays relative to how complicated systems are.  
Benchmarking yourself is the only reasonable defense against this very 
common problem.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books

view thread (6+ messages)  latest in thread

Message-ID: <4D589BFC.5040608@2ndquadrant.com>
Permalink:  ../4D589BFC.5040608@2ndquadrant.com/
Also on:    postgresql.org/message-id/4D589BFC.5040608@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: greg@2ndquadrant.com, kraj@servoyant.com, keith@fluentmobile.com
  Subject: Re: how do you manage postgres 9's postgres process's memory
  In-Reply-To: <4D589BFC.5040608@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox