Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 6095464219B
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 10 Feb 2010 00:39:29 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 56323-04-5
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 10 Feb 2010 04:39:18 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25])
	by mail.postgresql.org (Postfix) with ESMTP id C635D641DCD
	for <pgsql-performance@postgresql.org>;
	Wed, 10 Feb 2010 00:38:57 -0400 (AST)
Received: by qw-out-2122.google.com with SMTP id 5so1013681qwd.61
	for <pgsql-performance@postgresql.org>;
	Tue, 09 Feb 2010 20:38:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:from:date:message-id:subject:to:cc:content-type;
	bh=far62FsUY4i7h1LpAFCBIpFoLSyBM1R67qEBep77wvs=;
	b=VzVc4uDpE6XqcK9DJAMlEsOwfcQggrZ3oABYN/PCrTZ8Ub/Z70tWdItdD6pT7oOcZO
	6cxCpdDVQVA+RHmQF6W8xh1LkORvT5Knpg43bGcWcTFW+jeJKi5dfA8kdAw85LQQZ0Qb
	hKF94FVFhh8SgCmC+62OFds1QCKUrrlAnIC+I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	b=OdkaaMdCm54wb+D+9vaouF1ptGG1meSQUYZ7gu8ldQIqLkSrh++nEIU6stzjG08i0Q
	IJZj7o9uP8HXwc6pvCrLXPE+0Vz7b/8bVqNj9vKDa359OCxNih7tmH3Ih3Z/AgP7Q5rT
	RLCs/dgzpmGZgUKkEsuGF96G6c12gnOxa1seM=
MIME-Version: 1.0
Received: by 10.229.218.204 with SMTP id hr12mr1535970qcb.101.1265776737096;
	Tue, 09 Feb 2010 20:38:57 -0800 (PST)
In-Reply-To: 
 <OFE0550409.E8DBE5B8-ON652576C6.0014526C-652576C6.001716AC@ibsplc.com>
References: 
 <OFE0550409.E8DBE5B8-ON652576C6.0014526C-652576C6.001716AC@ibsplc.com>
From: Amitabh Kant <amitabhkant@gmail.com>
Date: Wed, 10 Feb 2010 10:08:37 +0530
Message-ID: <84b68b3d1002092038g52428df3u97df2838e07ebc73@mail.gmail.com>
Subject: Re: PostgreSQL - case studies
To: Jayadevan M <Jayadevan.Maymala@ibsplc.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Content-Type: multipart/alternative; boundary=00163630e88bc79767047f379c72
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.097 tagged_above=-10 required=5 tests=AWL=0.501,
	BAYES_00=-2.599, HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 201002/148
X-Sequence-Number: 37569

--00163630e88bc79767047f379c72
Content-Type: text/plain; charset=ISO-8859-1

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

--00163630e88bc79767047f379c72
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Wed, Feb 10, 2010 at 9:39 AM, Jayadevan M <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:Jayadevan.Maymala@ibsplc.com">Jayadeva=
n.Maymala@ibsplc.com</a>&gt;</span> wrote:<br><div>=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px sol=
id rgb(204, 204, 204); padding-left: 1ex;">

<font face=3D"sans-serif" size=3D"2">Any feedback - a few sentences with
the db size, =A0tps, h/w necessary to support that, and acceptable down-tim=
e,
type of application etc will be greatly appreciated.</font>
<br><font face=3D"sans-serif" size=3D"2">Our products are not of the blog/s=
ocial
networking type, but more of on-line reservation type where half an hour
down-time can lead to significant revenue losses for customers.</font>
<br><font face=3D"Trebuchet MS" size=3D"2">Thank you,</font>
<br><font face=3D"Trebuchet MS" size=3D"2">Jayadevan</font>
<br><br></blockquote></div><br>I don&#39;t have experience with DB size gre=
ater than 25-26 GB at the moment, but Postgres surely=A0 has no problems ha=
ndling my requirements. Mind you, this Was on a stock Postgresql server run=
ning on FreeBSD 7.x without any optimizations. Didn&#39;t seen any=A0 downt=
ime apart from the ones that I goofed up. H/w config was dual processor Xeo=
n/8GB RAM and a single=A0 SAS 15K disk (146 GB). The rig has been upgraded =
last week, but it ran fine for more than 18 months.<br>

<br>That said, we run an application which generates around 170-200 transac=
tions 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.<br>

<br>With regards<br><br>Amitabh<br><br><br>

--00163630e88bc79767047f379c72--