Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GetCapabilities request is extremely slow when “OWS_LAYER_GROUP” is used #5081

Closed
aabhayas opened this issue Mar 19, 2015 · 4 comments
Closed

GetCapabilities request is extremely slow when “OWS_LAYER_GROUP” is used #5081

aabhayas opened this issue Mar 19, 2015 · 4 comments
Milestone
7.0 Release

Comments

@aabhayas
Copy link
Contributor

GetCapabilities request is extremely slow when the Mapfile has nested layers using “OWS_LAYER_GROUP”. This bug exists from the version 6.2 of Mapserver.

Following link has more details of this bug.

http://osgeo-org.1560.x6.nabble.com/Re-Getcapabilities-extremely-slow-in-version-6-4-1-td5191374.html

I have uploaded two map files and two map part files which can be used to reproduce this bug.

http://osgeo-org.1560.x6.nabble.com/file/n5194857/layer_group.map
http://osgeo-org.1560.x6.nabble.com/file/n5194857/layer_group.part
http://osgeo-org.1560.x6.nabble.com/file/n5194857/no_layer_group.map
http://osgeo-org.1560.x6.nabble.com/file/n5194857/no_layer_group.part

Map file layer_group.map uses layer_group.map.part which has LAYER_GROUPS defined.

Map file no_layer_group.map uses no_layer_group.map.part which has no LAYER_GROUPS defined.

I use the following command line in my server to time the getcapabilities requests.

time /web/cgi-bin/mapserv -nh "QUERY_STRING=map=/web/ms4w/apps/tutorial/htdocs/layer_group.map&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities"

time /web/cgi-bin/mapserv -nh "QUERY_STRING=map=/web/ms4w/apps/tutorial/htdocs/no_layer_group.map&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities"
aabhayas added a commit to aabhayas/mapserver that referenced this issue Apr 29, 2015
@aabhayas
This patch is to fix the issue "GetCapabilities request is extremely …
134fcf7 
…slow when “OWS_LAYER_GROUP” is used"

MapServer#5081.

Changed the code to create a unique set of groups and then compare them with layer names to avoid multiple passes through layer names.
@aabhayas aabhayas mentioned this issue Apr 29, 2015
Merged
@tbonfort
Copy link
Member

fixed with #5094

@tbonfort tbonfort added this to the 7.0 Release milestone Feb 23, 2016
@tomkralidis
Copy link
Member

Is/should this be backported to 6.4.x?

@aabhayas
Copy link
Contributor Author

Hi

I think we should backport this to 6.4

Regards
Anuruddha Abhayasinghe
[Description: Description: Description: Description: http://web.bom.gov.au/eiab/publishing/images/bureau_logo.gif]
Geospatial Data and Services
Delivery Section / Build Branch
Bureau of Meteorology
GPO Box 1289 Melbourne VIC 3001
Level 6, 700 Collins Street, Docklands VIC 3008
Tel: +61 3 9669 4589 | aabhayas@bom.gov.aumailto:aabhayas@bom.gov.au
www.bom.gov.auhttp://www.bom.gov.au/

From: Tom Kralidis [mailto:notifications@github.com]
Sent: Thursday, 14 April 2016 5:59 AM
To: mapserver/mapserver
Cc: Anuruddha Abhayasinghe
Subject: Re: [mapserver/mapserver] GetCapabilities request is extremely slow when “OWS_LAYER_GROUP” is used (#5081)

Is/should this be backported to 6.4.x?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/5081#issuecomment-209622256

tomkralidis pushed a commit that referenced this issue Apr 18, 2016
@aabhayas @tomkralidis
This patch is to fix the issue "GetCapabilities request is extremely …
55558b3 
…slow when “OWS_LAYER_GROUP” is used"

#5081.

Changed the code to create a unique set of groups and then compare them with layer names to avoid multiple passes through layer names.
@tomkralidis
Copy link
Member

Backported to branch-6-4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
7.0 Release
Development

No branches or pull requests
3 participants
@tbonfort @tomkralidis @aabhayas