| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Timothy Glover <sion(at)greenbank(dot)net(dot)au> |
| Cc: | Postgres <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Postgresql / Threads / Scalability |
| Date: | 2000-03-05 14:15:41 |
| Message-ID: | Pine.LNX.4.21.0003051459150.347-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Carbaugh | 2000-03-05 19:52:14 | Re: [GENERAL] RE: Help with installing 6.5.3 on RedHat6.1 - specifying template |
| Previous Message | Peter Eisentraut | 2000-03-05 14:15:28 | Re: [GENERAL] ERROR: copyObject: don't know how to copy 704 |