Also using mapscript you can integrate mapserver with application by saving mapfile into database and letting application manage the mapserver configuration, grant access to authenticaded session clients<br>You will lose speed but win maintenance.<br>
I do not really like to update the mapfile, then the tilecache then seed tiles again for each small change.<br><br><div class="gmail_quote">2012/11/7 Umberto Nicoletti <span dir="ltr"><<a href="mailto:umberto.nicoletti@gmail.com" target="_blank">umberto.nicoletti@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The performance point being made clear by Thomas I think I should mention a couple of (mostly in functionality) advantages that the WxS wrappers might have against cgi/fastcgi:<div>
<br><div>1. it is easy to extend the wrapper to add accounting, logging, caching. True, accounting and logging can also be accomplished simply by processing the web server log files but that requires extra software and might not be easy to impement in complex situations (think a cached request costs x and a non-cached y)</div>
</div><div><br></div><div>2. request preprocessing: filtering layers, redirecting</div><div><br></div><div>3. image/response prostprocessing: caching, assembling, watermarking,...</div><div><br></div><div>Umberto</div><div>
<br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 7, 2012 at 10:15 AM, thomas bonfort <span dir="ltr"><<a href="mailto:thomas.bonfort@gmail.com" target="_blank">thomas.bonfort@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">- testing against cgi isn't really an objective test, but even so the differences will iron out as soon as the actual workloads are not trivial (i.e. if you're just benchmarking getcapabilities then sure, mapscript keeping in memory your mapfile will be orders of magnitude faster than cgi. switching to complex map draws will show very similar performance between both options)<div>
- using fastcgi will somewhat iron out the differences on trivial workloads</div><div class="im"><div>- certain mapscript scripts will leak non trivial amounts of memory, forcing server restarts periodically if you don't have an infinite amount of memory available.</div>
<div><br></div></div><div>with all that said, my recommendation is to stick with cgi/fastcgi unless you have very specific needs that force you to use mapscript.</div><span class="HOEnZb"><font color="#888888"><div><br></div>
<div>--</div><div>thomas</div></font></span><div><div class="h5"><div>
<div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Nov 7, 2012 at 9:42 AM, Umberto Nicoletti <span dir="ltr"><<a href="mailto:umberto.nicoletti@gmail.com" target="_blank">umberto.nicoletti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have tested cgi against python mapscript (with mod_python) and the performance improvement, as expected, is massive.<div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 7, 2012 at 8:53 AM, Spirifer <span dir="ltr"><<a href="mailto:ready945@gmail.com" target="_blank">ready945@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I would to use MapServer to create WMS/WFS services.<br>
<br>
I think to compare 2 systems to produce services:<br>
1) Apache + MapServer CGI + static mapfile (.map)<br>
2) Apache + MapScript PHP + map configuration in cache<br>
<br>
Somebody has tested the performance between the mapfile and MapScript ?<br>
<br>
Thanks.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://osgeo-org.1560.n6.nabble.com/Mapfile-VS-MapScript-performance-tp5014463.html" target="_blank">http://osgeo-org.1560.n6.nabble.com/Mapfile-VS-MapScript-performance-tp5014463.html</a><br>
Sent from the Mapserver - User mailing list archive at Nabble.com.<br>
_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
<br></blockquote></div><br></div>
</div></div></div></div></blockquote></div><br></div>
<br>_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
<br></blockquote></div><br>