Re: Partitioning Vs. Split Databases - performance? - Mailing list pgsql-general

From Marc Evans
Subject Re: Partitioning Vs. Split Databases - performance?
Date
Msg-id 20061221150913.B61328@me.softwarehackery.com
Whole thread Raw
In response to Re: Partitioning Vs. Split Databases - performance?  (Vlad <marchenko@gmail.com>)
List pgsql-general
On Thu, 21 Dec 2006, Vlad wrote:

> On 12/21/06, Ron Johnson <ron.l.johnson@cox.net> wrote:
>>
>>
>> >> Given the same physical hardware, which one is likely to perform
>> better? Does
>> >> it make any difference? Does using separate databases use more RAM than
>> a
>> >> single database with a bunch of different tables?
>>
>> Config files are global, so I doubt it.
>>
>
> if it's a web app with persistent connections, then splitting onto several
> databases may consume more RAM. Example: 100 apache clients connected to 3
> databases creates 300 forked postmaster processes ; vs 100 apache clients
> connected to the same DB using three schemas only takes 100 postmasters
>
> --  Vlad

Using something like pgpool between the web servers and the DB should help
with that scaling problem...

- Marc

pgsql-general by date:

Previous
From: Tomasz Ostrowski
Date:
Subject: Re: Password strength requirements
Next
From: "Shoaib Mir"
Date:
Subject: Re: Partitioning Vs. Split Databases - performance?