Thread: Many databases on a PostgreSQL server
Hello, we are developing web applications and are hosting the databases of these applications on our MS SQL server. There are about 50 of them at the moment, but the traffic is not very large (the average is a few tens requests per hour and database). We are considering switching to PostgreSQL, but we would like to know if it handles more than a few databases on a single server well. If there's anyone here operating lots of databases on a server, we'd be glad to hear your experience. Thank you, Andrei Badea MagicWare, Ltd.
Andrei Badea wrote: > Hello, > > we are developing web applications and are hosting the databases of > these applications on our MS SQL server. There are about 50 of them at > the moment, but the traffic is not very large (the average is a few tens > requests per hour and database). > > We are considering switching to PostgreSQL, but we would like to know if > it handles more than a few databases on a single server well. If there's > anyone here operating lots of databases on a server, we'd be glad to > hear your experience. Sure. You can do lots of databases, and lot of servers running on different ports too. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Oops! andrei.badea@magicware.cz (Andrei Badea) was seen spray-painting on a wall:
> we are developing web applications and are hosting the databases of
> these applications on our MS SQL server. There are about 50 of them at
> the moment, but the traffic is not very large (the average is a few
> tens requests per hour and database).
>
> We are considering switching to PostgreSQL, but we would like to know
> if it handles more than a few databases on a single server well. If
> there's anyone here operating lots of databases on a server, we'd be
> glad to hear your experience.
There can be some peculiar interactions if there are databases with
substantially different traffic patterns sharing a backend (and
therefore shared buffers); that should only be particularly important
if traffic is heavy.
Your situation doesn't sound like it ought to be terribly challenging,
except at those inevitable moments when your system gets hit by some
sort of "thundering herd" of updates, and it's hard to avoid that
problem...
--
output = ("cbbrowne" "@" "cbbrowne.com")
http://www.ntlug.org/~cbbrowne/spreadsheets.html
In a world without fences, who needs Gates?
Andrei, > we are developing web applications and are hosting the databases of > these applications on our MS SQL server. There are about 50 of them at > the moment, but the traffic is not very large (the average is a few tens > requests per hour and database). No problem. And, to be quite frank, if MSSQL can handle it, we can handle it easily. You could run into issues when you get up to, say, 500 databases. But not at 50 ... heck, I think I have that many on my testing server. -- Josh Berkus Aglio Database Solutions San Francisco