pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff <threshar@torgo.978.org>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: pgsql-performance@postgresql.org
Cc: Anjan Dave <adave@vantage.com>
Cc: fred@redhotpenguin.com
Cc: William Yu <wyu@talisys.com>
Cc: Chris Ruprecht <chris@ruprecht.org>
Subject: Re: Scaling further up
Date: Tue, 2 Mar 2004 21:07:10 -0500
Message-ID: <7AACCD10-6CB7-11D8-AD74-000393D1F76E@torgo.978.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0403021534160.5218-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0403021534160.5218-100000@css120.ihs.com>


On Mar 2, 2004, at 5:36 PM, scott.marlowe wrote:

> Some folks on the list have experience with Postgresql on Solaris, and
> they generally say they use Solaris not for performance reasons, but 
> for
> reliability reasons.  I.e. the bigger Sun hardware is fault tolerant.
>
Solaris isn't nearly as bad for PG as it used to be.

But as you say - the #1 reason to use sun is reliability. (In my case, 
it was because we had a giant sun laying around :)

I'm trying to remember exactly what happens..  but I know on sun if it 
had a severe memory error it kills off processes with data on that dimm 
(Since it has no idea if it is bad or not.  Thanks to ECC this is very 
rare, but it can happen.).  I want to say if a CPU dies any processes 
running on it at that moment are also killed.  but the more I think 
about that th emore I don't think that is the case.

As for x86.. if ram or a cpu goes bad you're SOL.

Although opterons are sexy you need to remember they really are brand 
new cpus - I'm sure AMD has done tons of testing but sun ultrasparc's 
have been in every situation conceivable in production.   If you are 
going to really have thousands of users you probably want to bet the 
farm on something proven.

lots and lots of spindles
lots and lots of ram

You may also want to look into a replication solution as a hot backup.

--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/




view thread (35+ messages)  latest in thread

Message-ID: <7AACCD10-6CB7-11D8-AD74-000393D1F76E@torgo.978.org>
Permalink:  ../7AACCD10-6CB7-11D8-AD74-000393D1F76E@torgo.978.org/
Also on:    postgresql.org/message-id/7AACCD10-6CB7-11D8-AD74-000393D1F76E@torgo.978.org

 · 

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-performance@postgresql.org
  Cc: threshar@torgo.978.org, scott.marlowe@ihs.com, adave@vantage.com, fred@redhotpenguin.com, wyu@talisys.com, chris@ruprecht.org
  Subject: Re: Scaling further up
  In-Reply-To: <7AACCD10-6CB7-11D8-AD74-000393D1F76E@torgo.978.org>

* 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