High volume use of postGres

From: "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: High volume use of postGres
Date: 2003-08-10 22:03:50
Message-ID: 71E37EF6B7DCC1499CEA0316A25683280105704B@loki.globexplorer.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


I've been charged with investigating postGIS as a replacement for our current Informix runtime (9.3), which uses the Spatial blade. Currently we use two Sun Sparc/Ultra 80 boxes with 3 CPUS dedicated to Informix.

We use our database to calculate the image files we have within a given area (ST_Union, Intersect and the like).

Originally this company tried Oracle, but, as the Firesign Theater put it, "He's no fun, he fell right over!" ... Informix works well but charges a hefty amount for each runtime CPU.

Our databases are not particularly large -- only about 500,000 rows in the larger ones, but we're running more than a million hits a day, not evenly spread, natch so at peak we need a lot of capacity.

Are there documents on performance of postGres on various platforms that I might be able to get some ideas from ? Such issues as multiple CPU vs single CPU, Operating System -- we're leaning towards Linux of some flavor but also have some Sun servers (not as hefty as our current runtime database servers) -- would be of interest.

Any suggestions from users that have/are really beating up postGIS/postgres would be welcome ! (for instance, cleaning up a busy database, supporting multiple servers, etc.)

Thanks,

Greg Williamson
DBA
GlobeXplorer LLC

Browse pgsql-general by date

  From Date Subject
Next Message Raymond 2003-08-10 22:06:00 Concatenating String Literals in pgsql
Previous Message Gregory S. Williamson 2003-08-10 21:52:25 dbmirror -- recovery question