<br><br><div class="gmail_quote">2012/6/28 Smith, Michael ERDC-RDE-CRREL-NH <span dir="ltr"><<a href="mailto:Michael.Smith@erdc.dren.mil" target="_blank">Michael.Smith@erdc.dren.mil</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div>The biggest impact will be the total amount of data involved. The number of vertices you reported earlier seemed quite large for most scales. I'd consider doing some generalization for higher zoom levels.</div></div>
</blockquote><div><br></div><div>I think I will do that. I didn't notice such an impact within our Linux environments.</div><div>The timing is closely related to the number of vertices:</div><div><br></div><div>1 polygon (836 vertices):</div>
<div>0.108s</div><div>16 polygons (836 vertices each):</div><div>0.404s</div><div><br></div><div><br></div><div>1 polygon (19594 vertices):</div><div>0.627s</div><div>16 polygons (19594 vertices each)</div><div>7.672s</div>
<div>Delta time between msPostGISLayerNextShape 0.45s</div><div><br></div><div>As you can see, the delta is similar to calling the 16 smaller poligons, which sum to 13376 vertices.</div><div><br></div><div>giovanni</div><div>
<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div><br>
</div>
<div>Mike</div><span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>
<div>
<div>
<div>-- </div>
<div>Michael Smith</div>
</div>
<div>US Army Corps</div>
<div>Remote Sensing GIS/Center</div>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
</font></span><span><span class="HOEnZb"><font color="#888888">
<div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span>"G. Allegri" <<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, June 28, 2012 9:45 AM<br>
<span style="font-weight:bold">To: </span>Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com" target="_blank">jmckenna@gatewaygeomatics.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:ms4w-users@lists.maptools.org" target="_blank">ms4w-users@lists.maptools.org</a>" <<a href="mailto:ms4w-users@lists.maptools.org" target="_blank">ms4w-users@lists.maptools.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [MS4W-Users] slow access to PostGIS layer<br>
<span style="font-weight:bold">Resent-From: </span>Michael Smith <<a href="mailto:michael.smith@usace.army.mil" target="_blank">michael.smith@usace.army.mil</a>><br>
</div></font></span><div><div class="h5">
<div><br>
</div>
<div>
<div>The first important bottleneck is reprojection, obviously.
<div>Removing the reprojection from 23032 to 900913, the time is dropped from 7.2s to 4.6s.</div>
<div><br>
</div>
<div>I go on...</div>
<div><br>
</div>
<div>giovanni<br>
<br>
<div class="gmail_quote">2012/6/28 G. Allegri <span dir="ltr"><<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I will go on testing.
<div>In the meantime, the same exact shp2img command run on Linux gives much better performances, and OGR outperforms POSTGIS again.</div>
<div><br>
</div>
<div>Windows</div>
<div>POSTGIS: 7.2s</div>
<div>OGR: 2.7s</div>
<div><br>
</div>
<div>Linux</div>
<div>POSTGIS: 2.5s</div>
<div>OGR: 1.0s</div>
<div><br>
</div>
<div>giovanni</div>
<div>
<div>
<div><br>
<div class="gmail_quote">2012/6/28 Jeff McKenna <span dir="ltr"><<a href="mailto:jmckenna@gatewaygeomatics.com" target="_blank">jmckenna@gatewaygeomatics.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
And how did another small polygon file do? (it could be a problem with<br>
your one table)<br>
<span><font color="#888888"><br>
-jeff<br>
</font></span>
<div><br>
<br>
> - load another small polygon shapefile into your PG, then try that with<br>
> MapServer<br>
><br>
<br>
<br>
</div>
<div>
<div>--<br>
Jeff McKenna<br>
MapServer Consulting and Training Services<br>
<a href="http://www.gatewaygeomatics.com/" target="_blank">http://www.gatewaygeomatics.com/</a><br>
<br>
<br>
<br>
_______________________________________________<br>
MS4W-Users mailing list<br>
<a href="mailto:MS4W-Users@lists.maptools.org" target="_blank">MS4W-Users@lists.maptools.org</a><br>
<a href="http://lists.maptools.org/mailman/listinfo/ms4w-users" target="_blank">http://lists.maptools.org/mailman/listinfo/ms4w-users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div></div></span>
</div>
</blockquote></div><br>