Re: [GENERAL] Postgresql / Threads / Scalability - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: [GENERAL] Postgresql / Threads / Scalability
Date
Msg-id Pine.LNX.4.21.0003051459150.347-100000@localhost.localdomain
Whole thread Raw
In response to Postgresql / Threads / Scalability  ("Timothy Glover" <sion@greenbank.net.au>)
List pgsql-general
Timothy Glover writes:

> At work we are considering whether to switch to oracle or continue
> with postgresql. We currently use postgresql, with no problems and
> excellent response time (with data mining). But we are wondering what
> happens when the database gets huge. Currently its run on a p3/300
> with 198 megs of ram, and it services 80 hospital locations.

If that means a lot of concurrent clients you want to get a lot more CPUs
it seems.

I'm not sure what you consider a huge database but there are instances of
databases of far more than 10GB. Big hardware and a better OS will help.


--
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [GENERAL] Median, Quartile and Percentile Aggregate Functions
Next
From: Peter Eisentraut
Date:
Subject: Re: [GENERAL] ERROR: copyObject: don't know how to copy 704