At 22:42 24/09/00 -0300, Jeff MacDonald wrote:
>and there are 2 592 000
>seconds in a month.. that's a little over
>
>that's 1.728 seconds per query..
>
>short answer .. postgres can do it, it depends
>on the machine
You need to be a little carefull here; I'd guess the peak will be at least
4x the average, and may be 10x or even 100x. It may still come down to the
machine power, but the most likely TPS would be 2.5, 5 and 50, which are
still probably quite doable.
I'd also question the original numbers: an enquiry load that is only twice
the update load would be quite unusual. But I've never had anything to do
with a high volume billing system like a phone system. I am more used to a
10:1 ratio, which starts making the upper estimate TPS look a little harder
to achieve. I don't know what PG is really capable of - the recent GB
benchmarks suggest it should work, but it will start to depend on the
complexity of the queries, I think.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
