From: Matt Chambers <chambers@imageworks.com>
To: pgsql-performance@postgresql.org
Subject: db performance/design question
Date: Wed, 12 Sep 2007 13:33:25 -0700
Message-ID: <46E84D15.8020600@imageworks.com> (raw)
I'm designing a system that will be doing over a million inserts/deletes
on a single table every hour. Rather than using a single table, it is
possible for me to partition the data into multiple tables if I wanted
to, which would be nice because I can just truncate them when I don't
need them. I could even use table spaces to split the IO load over
multiple filers. The application does not require all this data be in
the same table. The data is fairly temporary, it might last 5 seconds,
it might last 2 days, but it will all be deleted eventually and
different data will be created.
Considering a single table would grow to 10mil+ rows at max, and this
machine will sustain about 25mbps of insert/update/delete traffic 24/7 -
365, will I be saving much by partitioning data like that?
--
-Matt
<http://twiki.spimageworks.com/twiki/bin/view/Software/CueDevelopment;
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: chambers@imageworks.com
Subject: Re: db performance/design question
In-Reply-To: <46E84D15.8020600@imageworks.com>
* 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