From: | Marc Evans <Marc(at)SoftwareHackery(dot)Com> |
---|---|
To: | Vlad <marchenko(at)gmail(dot)com> |
Cc: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Partitioning Vs. Split Databases - performance? |
Date: | 2006-12-21 20:10:01 |
Message-ID: | 20061221150913.B61328@me.softwarehackery.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 21 Dec 2006, Vlad wrote:
> On 12/21/06, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Shoaib Mir | 2006-12-21 20:14:28 | Re: Partitioning Vs. Split Databases - performance? |
Previous Message | Tomasz Ostrowski | 2006-12-21 20:04:33 | Re: Password strength requirements |