pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: matt <matt@ymogen.net>
To: Bill Moran <wmoran@potentialtech.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware recommendations to scale to silly load
Date: 27 Aug 2003 15:37:14 +0100
Message-ID: <1061995033.15800.138.camel@gibraltar.mattclark.net> (raw)
In-Reply-To: <3F4CBD8A.4050309@potentialtech.com>
References: <1061948112.15800.53.camel@gibraltar.mattclark.net>
	<3F4C1364.6080602@potentialtech.com>
	<1061990263.15800.124.camel@gibraltar.mattclark.net>
	<3F4CBD8A.4050309@potentialtech.com>

> Don't know how "cheap" they are.
> 
> I have an app that does large batch updates. I found that if I dropped
> the indexes, did the updates and recreated the indexes, it was faster
> than doing the updates while the indexes were intact.

Yeah, unfortunately it's not batch work, but real time financial work. 
If I drop all the indexes my select performance goes through the floor,
as you'd expect.

> Does noatime make much difference on a PostgreSQL database?  I haven't
> tested that yet.

Yup, it does.  In fact it should probably be in the standard install
documentation (unless someone has a reason why it shouldn't).  Who
*cares* when PG last looked at the tables?  If 'nomtime' was available
that would probably be a good thing too.

> Can you split it onto multiple boxes?  Some database layouts lend themselves
> to this, others don't.  Obviously you can't do joins from one server to
> another, so you may lose more in multiple queries than you gain by having
> multiple servers.  It's worth looking into though.

I'm considering that.  There are some tables which I might be able to
split out.  There amy even be some things I can pull from the DB
altogether (session info in particular, so long as I can reliably send a
given user's requests to the same app server each time, bearing in mind
I can't see the cookies too easily because 50% of the requests are over
SSL)

> I know my answers aren't quite the ones you were looking for, but my
> experience is that many people try to solve poor application design
> by simply throwing bigger hardware at the problem.  It appears as though
> you've already done your homework, though.

Well, I *hope* that's the case!  The core issue is simply that we have
to deal with an insane load for 1 hour a week, and there's just no
avoiding it.

Maybe I can get Sun/HP/IBM to lend some gear (it's a pretty high-profile
site).




view thread (45+ messages)  latest in thread

Message-ID: <1061995033.15800.138.camel@gibraltar.mattclark.net>
Permalink:  ../1061995033.15800.138.camel@gibraltar.mattclark.net/
Also on:    postgresql.org/message-id/1061995033.15800.138.camel@gibraltar.mattclark.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: matt@ymogen.net, wmoran@potentialtech.com
  Subject: Re: Hardware recommendations to scale to silly load
  In-Reply-To: <1061995033.15800.138.camel@gibraltar.mattclark.net>
  References: <1061948112.15800.53.camel@gibraltar.mattclark.net> <3F4C1364.6080602@potentialtech.com> <1061990263.15800.124.camel@gibraltar.mattclark.net> <3F4CBD8A.4050309@potentialtech.com> <1061995033.15800.138.camel@gibraltar.mattclark.net>

* 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