<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Try using Fast CGI, it should improve your latency problem you
are seeing. It is also possible that using other raster formats could help.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Good luck! M<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span lang=PT-BR style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>--------------<o:p></o:p></span></p>
<p class=MsoNormal><span lang=PT-BR style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Marcelo Simas Oliveira<o:p></o:p></span></p>
<p class=MsoNormal><span lang=PT-BR style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>GeoStats LP<o:p></o:p></span></p>
<p class=MsoNormal><span lang=PT-BR style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>530 Means St., Ste. 310<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Atlanta, Georgia 30318<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>(404) 588-1004<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>www.geostats.com<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'>
mapserver-users-bounces@lists.osgeo.org
[mailto:mapserver-users-bounces@lists.osgeo.org] <b>On Behalf Of </b>Rahkonen
Jukka<br>
<b>Sent:</b> Friday, December 12, 2008 10:01 AM<br>
<b>To:</b> mapserver-users@lists.osgeo.org<br>
<b>Subject:</b> [mapserver-users] How to make MapServer WMS super fast?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Hi,</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Are there any effective tricks for making MapServer to
Top-Fuel class? We have now a typical ms4w installation on a rather
good server platform with SCSI drives and 2 four-core processors running
on Windows 2003 server. Our images are tiled, uncompressed geotiffs with
overviews, vector sample data set is shapefile with shptree index. I have
a shortened epsg file and my mapfile is extra short. Bandwith is not the limit.
We are getting out now about 450 orthoimage pictures per minute (size 500 by
500 pixels) and 550 pictures from the vector layer in png24 image format.
I consider that rather good, but we are required to reach 20 images per second,
thus 1200 images per minute or 0.05 seconds per image. I wonder if
anybody has tuned MapServer that far.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I am willing to try however exotic solutions to reach the 20 WMS
output images/second goal if somebody could suggest me what to try next.
In our system there seems to be about 0.1 second ballast with WMS getMap
requests and I cannot get any faster response even if I try with on empty data
layer with nothing to render. Have anybody tried to keep mapfile,
epsg-file or even tileindex files in RAM drive? </span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Having about 20 parallel users seems to be optimal for our
server and if I drive just WMS getCapabilities request against my mapfile
I can get about 1300 responses per minute. That leads me to think that
1200 rendered images per minute might be possible to reach with optimal set-up.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>-Jukka Rahkonen-</span><o:p></o:p></p>
</div>
</body>
</html>