pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <pg@rbt.ca>
To: Suchandra Thapa <s-thapa-11@alumni.uchicago.edu>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: performance optimzations
Date: Thu, 13 Nov 2003 08:47:33 -0500
Message-ID: <1068731245.31569.152.camel@jester> (raw)
In-Reply-To: <1068703124.12978.27.camel@hepcat>
References: <1068658430.1071.42.camel@hepcat>
	<1068661380.30452.17.camel@jester>
	<1068663070.5193.21.camel@hepcat>
	<1068698132.31569.46.camel@jester>
	<1068703124.12978.27.camel@hepcat>

> > Most clients will be interested in say the last 7 days worth of data? 
> > Great.. Start out with 4GB ram on a good Dual CPU -- Opterons seem to
> > work quite well -- and make sure the motherboard can hold double that in
> > memory for an upgrade sometime next year when you've become popular.
> 
> Unfortunately, the hardware available is pretty much fixed in regards to
> the system.  I can play around with the raid configurations and have
> some limited choice in regards to the raid controller and number of
> drivers but that's about all in terms of hardware.    

Good luck then. Unless the configuration takes into account incremental
additions in ram and disk, sustained growth could get very expensive. I
guess that depends on the business plan expectations.

This just puts more emphasis to offload everything you can onto machines
that can multiply.

> The current file system holding the user and email information indicates
> the current data has about 64GB (70K accounts, I'm not sure how many are
> active but 50% might be good guess).  This seems to be somewhat of a
> steady state however.

35k clients checking their mail daily isn't so bad. Around 10 pages per
second peak load?




view thread (8+ messages)

Message-ID: <1068731245.31569.152.camel@jester>
Permalink:  ../1068731245.31569.152.camel@jester/
Also on:    postgresql.org/message-id/1068731245.31569.152.camel@jester

 · 

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: pg@rbt.ca, s-thapa-11@alumni.uchicago.edu
  Subject: Re: performance optimzations
  In-Reply-To: <1068731245.31569.152.camel@jester>

* 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