<!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: [UMN_MAPSERVER-USERS] Ideal web server configuration</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi Mike,<BR>
<BR>
It sounds like you are doing very similar things to us (chameleon, php_mapscript, AJAX, and postgresql). I'm nowhere near as qualified as some to answer this, but I would focus on:<BR>
<BR>
- at least two harddisks setup as RAID, to ensure fast reading speed. This will help a lot in general, especially reading large images from the disk.<BR>
- lower-clockspeed quad core processors (comparatively cheap), in preference of high-speed dual core processors, because you would expect many, shortlived, simultaneous processes, rather than just a few intensive long-lasting processes. An expensive dual-core buys you two quad core processors. We prefer the latter.<BR>
- 4GB of RAM is good, although we rarely need it all.<BR>
<BR>
I guess it depends on what you call a "modest budget", but I would focus on what you bottlenecks would be. In your case, I'd say disk speed (especially for chameleon, which does lots of reads and writes), then CPU, then RAM. We recently bought our server based on these principles, and it works well for us.<BR>
<BR>
regards,<BR>
<BR>
Jacob<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: UMN MapServer Users List on behalf of Mike Leahy<BR>
Sent: Tue 22/01/2008 09:23<BR>
To: MAPSERVER-USERS@LISTS.UMN.EDU<BR>
Subject: [UMN_MAPSERVER-USERS] Ideal web server configuration<BR>
<BR>
Hello list,<BR>
<BR>
I'm looking at ordering a new web server for the office I'm in, and I'm<BR>
wondering if anyone has any suggestions regarding the hardware that I<BR>
should choose. Normally, I've worked with hardware that was already<BR>
available to me, so I've never really had to put consideration into this<BR>
upfront. I know this may be a bit off-topic for this list, but I figure<BR>
people on this list will likely have some experience with this.<BR>
<BR>
The application we're working on will involve multiple simultaneous<BR>
users interacting with a chameleon-based map interface. The<BR>
communication between the client and server will generally involve AJAX<BR>
requests and downloading of updated map images generated by MapServer.<BR>
On the server side, we'll be running Apache, PHP (with MapScript), and a<BR>
PostgreSQL/PostGIS server that will be receiving frequent<BR>
queries/updates. There will likely be some high resolution imagery, as<BR>
well as a variety of vector layers used in the map that is displayed.<BR>
<BR>
Given that I have a relatively modest budget to work with, what I'd<BR>
really like to know is how I should prioritize the different hardware<BR>
specs that I can choose from (e.g., multiple CPUs/core, RAM, SATA/SAS<BR>
and/or RAID disk configurations, etc.).<BR>
<BR>
Thanks in advance for any suggestions,<BR>
Mike<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000>This email and any attachments are intended solely for the named recipient and are confidential. The copying or distribution of them or any information they contain by anyone other than the named recipient is prohibited. If you have received this document in error, please notify the sender and delete all copies from your computer system and destroy all hard copies. It is the recipient's responsibility to check this email and any attachments to this email for viruses before use.<br>
</font></td></tr></table>