<div dir="ltr"><div>Unofficial benchmark: 255 layers in 58 nested groups (using wms_layer_group) takes less than 200ms on Linux Kernel 3.5.0, Intel(R) Xeon(R) CPU E5-2630 @ 2.30GHz.<br><br>(It takes the terminal longer to print the 234 kB response XML than it takes MapServer in CGI mode to return the result.)<br><br>All layers in wms.map are of the form:<br></div><br><div> LAYER<br> NAME 'L119_all'<br><br> STATUS ON<br> TYPE RASTER<br><br> CONNECTIONTYPE WMS<br> CONNECTION "<a href="http://gis/datasets/ADDRESS/ADDRESS_RANGE/address_range.map">http://gis/datasets/ADDRESS/ADDRESS_RANGE/address_range.map</a>?"<br><br> PROJECTION<br> "init=epsg:26915"<br> END<br><br> METADATA<br> # WMS client connection options (input)<br> "wms_name" "all"<br> "wms_srs" "EPSG:26915"<br> "wms_server_version" "1.1.1"<br> "wms_format" "image/png"<br><br> # WMS Server options (output)<br> "wms_enable_request" "GetCapabilities GetMap GetFeatureInfo GetLegendGraphic"<br> "wms_title" "Address Ranges"<br> "wms_layer_group" "/Address"<br> #"wms_opaque" "0"<br> "wms_formatlist" "image/png, image/jpeg"<br> "wms_extent" "477594.70 4924010.29 497206.99 4941936.31"<br> "gml_include_items" "all"<br> END<br><br> TEMPLATE "dummy"<br> PROCESSING "RESAMPLE=AVERAGE"<br> END<br><br><br><!-- MapServer version 6.4.1 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=GD SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=THREADS SUPPORTS=GEOS INPUT=JPEG INPUT=POSTGIS INPUT=ORACLESPATIAL INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE --><br><br>time curl "<a href="http://gis/datasets/wms.map?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities">http://gis/datasets/wms.map?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities</a>" | grep 'queryable="1"' | wc<br> 255 1020 13728<br><br>real 0m0.151s<br>user 0m0.000s<br>sys 0m0.008s<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 5, 2015 at 3:58 PM, Jim Klassen <span dir="ltr"><<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I work with a mapfile designed to be a WMS proxy to organize all our
WMS sources (typically other mapfiles) into one point of access. It
has many layers makes extensive use of groups. In general testing
with curl and use with QGIS, I have not noticed the GetCapabilites
(or any other aspect of the configuration) to be slow. I am away
from the machine at the moment, but will run benchmarks tomorrow.<br>
<br>
The upstream sources and the proxy mapfile run under MapServer 6.4.1
(with some minimal patching).<div><div class="h5"><br>
<br>
<div>On 03/05/2015 12:33 PM, thomas bonfort
wrote:<br>
</div>
<blockquote type="cite">
<pre>IIRC, this happened when we introduced advanced layer groupings along with
inspire support in 6.2, and has to do with multiple passes through layers
to determine which ones to activate or not. I'd suspect the cost is
proportional to nlayers² which is why it comes up for folks with many
layers in their mapfiles.
Thomas.
On Mar 5, 2015 7:26 PM, "Lime, Steve D (MNIT)" <a href="mailto:Steve.Lime@state.mn.us" target="_blank"><Steve.Lime@state.mn.us></a>
wrote:
</pre>
<blockquote type="cite">
<pre>This is something I’d really like to see fixed. Any chance a test mapfile
could be developed and attached to a new ticket on github? Ideally I'd
start against 7.0 and then back-port if possible.
Steve
-----Original Message-----
From: <a href="mailto:mapserver-users-bounces@lists.osgeo.org" target="_blank">mapserver-users-bounces@lists.osgeo.org</a> [mailto:
<a href="mailto:mapserver-users-bounces@lists.osgeo.org" target="_blank">mapserver-users-bounces@lists.osgeo.org</a>] On Behalf Of Rahkonen Jukka (MML)
Sent: Wednesday, March 04, 2015 2:34 AM
To: aabhayas; <a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a>
Subject: Re: [mapserver-users] Getcapabilities extremely slow in version
6.4.1
Hi,
I have been wondering also why GetCapabilities response is so slow for us
nowadays and I have indeed added lots of groups to some services.
+1 from me for having a look at this issue.
We just installed 7.0-beta on our test server and GetCapabilities comes
slowly from that too. There are about 40 layers in the test service and
response time is about 8 seconds.
Sometimes I have been wondering if GetCapabilities could be cached and
controlled by some new CONFIG key. Cached GetCapabilities could be set to
be refreshed for example once per week/day/hour if there is a need to react
on changes in the data, and each time after the mapfile has been edited and
saved with a new timestamp.
-Jukka Rahkonen-
aabhayas wrote:
</pre>
<blockquote type="cite">
<pre>Hi
</pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre>Following up on my previous post we still want to use “OWS_LAYER_GROUP”
</pre>
</blockquote>
<pre>in our map files. We have large number of layers in our map file ( nearly
800).
</pre>
<blockquote type="cite">
<pre>Currently we are in the process of migrating our MapServer 5.4.2
</pre>
</blockquote>
<pre>environment in to MapServer 6.4.1.
</pre>
<blockquote type="cite">
<pre>In MapServer 6.4.1 GetCapabilities request takes more than 1 minute
</pre>
</blockquote>
<pre>compared
5 second in version 5.4.2. This makes the new environment unusable by our
clients.
</pre>
<blockquote type="cite">
<pre>Is there a possibility where someone in the MapServer development team
</pre>
</blockquote>
<pre>looks in to this and fix this issue.
</pre>
<blockquote type="cite">
<pre>Thanks
</pre>
</blockquote>
<pre>
--
View this message in context:
<a href="http://osgeo-org.1560.x6.nabble.com/Getcapabilities-extremely-slow-in-version-6-4-1-tp5189325p5191328.html" target="_blank">http://osgeo-org.1560.x6.nabble.com/Getcapabilities-extremely-slow-in-version-6-4-1-tp5189325p5191328.html</a>
Sent from the Mapserver - User mailing list archive at Nabble.com.
_______________________________________________
mapserver-users mailing list
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a>
_______________________________________________
mapserver-users mailing list
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a>
_______________________________________________
mapserver-users mailing list
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a>
</pre>
</blockquote>
<pre></pre>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
mapserver-users mailing list
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a></pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>