From: Jakab Laszlo <jakablaszlo@sofasoft.ro>
To: Justin Clift <justin@postgresql.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance issues for processing more then 150000
Date: Fri, 21 Feb 2003 11:59:24 +0200
Message-ID: <00e101c2d98f$ea9a32c0$0900000a@new> (raw)
References: <004501c2d97d$98927670$0900000a@new>
<0a6901c2d97f$ea1369d0$6500a8c0@fhp.internal>
<007c01c2d983$f3d60d70$0900000a@new>
<3E55EE62.6010909@postgresql.org>
> 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.
>
The main information is a barcode. The big table will have aprox 3 fields
(just id type fields).
Not so complex there will be mainly about 50 tables with all the info
totally normalized and with some around 10-20 tables which make the links
between them. Usually the join is starting form one much smaller table and
with left join goes trough the big table (barcodes) and maybe also on other
tables.
And then this table with barcode (this is the bigone with 150000
records/day) linked to other smaller tables. ( 1 bigger with aprox 7000
inserts/day).
> > 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.
Unfortunatelly the hardware budget should be keept as low as possible.
I was thinking is there could be reliable solution based on dual processor
and ATA 133 raid mirroring normally with some gigs of memory.
Thanks,
Jaki
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: jakablaszlo@sofasoft.ro, justin@postgresql.org
Subject: Re: performance issues for processing more then 150000
In-Reply-To: <00e101c2d98f$ea9a32c0$0900000a@new>
References: <004501c2d97d$98927670$0900000a@new> <0a6901c2d97f$ea1369d0$6500a8c0@fhp.internal> <007c01c2d983$f3d60d70$0900000a@new> <3E55EE62.6010909@postgresql.org> <00e101c2d98f$ea9a32c0$0900000a@new>
* 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