From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Kavan, Dan (IMS) <KavanD@imsweb.com>
Cc: postgres <pgsql-admin@postgresql.org>
Subject: Re: resource allocation ; postgresql-8.0
Date: Thu, 12 May 2005 14:13:12 -0500
Message-ID: <1115925192.22291.12.camel@state.g2switchworks.com> (raw)
In-Reply-To: <782D2A81EC812642B857B03B506E0B4432648E@granite.omni.imsweb.com>
References: <782D2A81EC812642B857B03B506E0B4432648E@granite.omni.imsweb.com>
On Thu, 2005-05-12 at 12:56, Kavan, Dan (IMS) wrote:
> Scott,
> If you had two applications that were each connecting to two different
> databases, have you found that it's beneficial to have to different
> instances of postgres running?
I haven't, but I could see where, if the workloads were very different,
it might be advantageous.
> I have a few reasons why I think it would be better. One, it would be
> beneficial to customize parameters for each application. They would be
> different sizes for example and they may each have different amounts of
> people connecting to them.
Possible. It really depends on how different they are. There are
benefits to having only one postmaster running, but since you've got
3gigs+ memory, the memory savings probably isn't one of them.
> Two, from a networking perspective, it may
> be faster ( 2 different ports rather than one )
I doubt that would be a big difference.
> Do you agree with those
> reasons or can you think of other reasons it would be wise?
Well, running two separate clusters under separate postgres superuser
account would afford the maximum in isolation. Plus you could easily
place each cluster on it's own storage to provide better performance and
keep them from interacting with each other. If, at some later date you
decide to put them on separate machines you're aleady halfway there.
> It seems
> like it would be more administrative work to have 2 different instances,
> so there may be some cons to that idea as well.
Exactly. You need to schedule separate vacuums for each, etc...
I tend to leave it on one cluster unless performance starts to become an
issue.
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-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, KavanD@imsweb.com
Subject: Re: resource allocation ; postgresql-8.0
In-Reply-To: <1115925192.22291.12.camel@state.g2switchworks.com>
References: <782D2A81EC812642B857B03B506E0B4432648E@granite.omni.imsweb.com> <1115925192.22291.12.camel@state.g2switchworks.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