<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [postgis-users] (no subject)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>This is sort of a broad question, especially without any details about the type of application (OLTP ? Data Warehouse ? What volumes in ? How many connections needed ? etc.).<BR>
<BR>
That said, it is a rare database that is limited by CPU power, although that can happen. If you can buy enough RAM to fit all (or most) of your data into memory then applications which are more-or-less read only will be very fast. (But writing data still needs to go to disk.)<BR>
<BR>
Mostly databases have issues moving lots of data to/from disk, so to that end I generally lean towards recommending lots of disks (more spindles better than sheer RPMs usually), battery backed cache if you can, both for speed and for safety, and don't use RAID5 unless your data is not very important.<BR>
<BR>
Try searching the PostgreSQL archives (see <<A HREF="http://www.postgresql.org/community/lists/">http://www.postgresql.org/community/lists/</A>> and performance list in particular) for previous questions like this. Since postGIS builds on the database engine for most purposes a good understanding of the database itself are useful.<BR>
<BR>
HTH,<BR>
<BR>
Greg Williamson<BR>
Senior DBA<BR>
GlobeXplorer LLC, a DigitalGlobe company<BR>
<BR>
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and must be protected in accordance with those provisions. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.<BR>
<BR>
(My corporate masters made me say this.)<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: postgis-users-bounces@postgis.refractions.net on behalf of Jennehag Åke<BR>
Sent: Fri 10/5/2007 3:42 AM<BR>
To: postgis-users@postgis.refractions.net<BR>
Subject: [postgis-users] (no subject)<BR>
<BR>
<BR>
<BR>
Hi all!<BR>
<BR>
<BR>
<BR>
I work with a cadastral map project i Kyrgyzstan. In this project we will usesPostGIS as the database to store the cadastral objects. What is the most important thing then buying a server to run PostGIS? Is it disk access? Memory? CPU? What are your experiences?<BR>
<BR>
<BR>
<BR>
Regards<BR>
<BR>
Åke Jennehag, Swedesurvey consultant (now in Kyrgyzstan)<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>