From: Amitabh Kant <amitabhkant@gmail.com>
To: Jayadevan M <Jayadevan.Maymala@ibsplc.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL - case studies
Date: Wed, 10 Feb 2010 10:08:37 +0530
Message-ID: <84b68b3d1002092038g52428df3u97df2838e07ebc73@mail.gmail.com> (raw)
In-Reply-To: <OFE0550409.E8DBE5B8-ON652576C6.0014526C-652576C6.001716AC@ibsplc.com>
References: <OFE0550409.E8DBE5B8-ON652576C6.0014526C-652576C6.001716AC@ibsplc.com>
On Wed, Feb 10, 2010 at 9:39 AM, Jayadevan M
<Jayadevan.Maymala@ibsplc.com>wrote:
> Any feedback - a few sentences with the db size, tps, h/w necessary to
> support that, and acceptable down-time, type of application etc will be
> greatly appreciated.
> Our products are not of the blog/social networking type, but more of
> on-line reservation type where half an hour down-time can lead to
> significant revenue losses for customers.
> Thank you,
> Jayadevan
>
>
I don't have experience with DB size greater than 25-26 GB at the moment,
but Postgres surely has no problems handling my requirements. Mind you,
this Was on a stock Postgresql server running on FreeBSD 7.x without any
optimizations. Didn't seen any downtime apart from the ones that I goofed
up. H/w config was dual processor Xeon/8GB RAM and a single SAS 15K disk
(146 GB). The rig has been upgraded last week, but it ran fine for more than
18 months.
That said, we run an application which generates around 170-200 transactions
per second (mix of select insert, update and delete). AFAIK, most of us
using Postgres are running some or the other critical application where
downtime has a significant cost attached to it.
With regards
Amitabh
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: amitabhkant@gmail.com, Jayadevan.Maymala@ibsplc.com
Subject: Re: PostgreSQL - case studies
In-Reply-To: <84b68b3d1002092038g52428df3u97df2838e07ebc73@mail.gmail.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