pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Clift <justin@postgresql.org>
To: Jakab Laszlo <jakablaszlo@sofasoft.ro>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance issues for processing more then 150000
Date: Fri, 21 Feb 2003 19:46:18 +1030
Message-ID: <3E55EE62.6010909@postgresql.org> (raw)
In-Reply-To: <007c01c2d983$f3d60d70$0900000a@new>
References: <004501c2d97d$98927670$0900000a@new>
	<0a6901c2d97f$ea1369d0$6500a8c0@fhp.internal>
	<007c01c2d983$f3d60d70$0900000a@new>

Jakab Laszlo wrote:
> Hello Chris,
>  
> I mean here 150000 inserts/day ( quickly grows constantly )...  - with 
> transactions and on the same table ... maybe after one significant 
> amount of time we can move the records of one year to one archive table ...
> And some 2-3 millions of selects / day ...

That's no problem at all, depending on:

  + How complex are the queries you're intending on running?

  + How will the data be spread between the tables?

  + The amount of data per row also makes a difference, if it is 
extremely large.


> I would like to know also some hardware related advice.

You're almost definitely going to be needing a SCSI or better RAID 
array, plus a server with quite a few GB's of ECC memory.

If you need to get specific about hardware to the point of knowing 
exactly what you're needing, you're likely best to pay a good PostgreSQL 
consultant to study your proposal in depth.

Hope this helps.

Regards and best wishes,

Justin Clift


> thanks,
> Jaki

-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi




view thread (8+ messages)  latest in thread

Message-ID: <3E55EE62.6010909@postgresql.org>
Permalink:  ../3E55EE62.6010909@postgresql.org/
Also on:    postgresql.org/message-id/3E55EE62.6010909@postgresql.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 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: justin@postgresql.org, jakablaszlo@sofasoft.ro, chriskl@familyhealth.com.au
  Subject: Re: performance issues for processing more then 150000
  In-Reply-To: <3E55EE62.6010909@postgresql.org>
  References: <004501c2d97d$98927670$0900000a@new> <0a6901c2d97f$ea1369d0$6500a8c0@fhp.internal> <007c01c2d983$f3d60d70$0900000a@new> <3E55EE62.6010909@postgresql.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