Benoit,
Thanks for your comment. In fact we are creating the runtime maps server side
sending an array of map definitions in the request as you suggest. Now to
reduce the load a little bit, I am only doing this for the maps that are to be
visible at startup of the application. When the user switches additional layers
on I add them to the session over http but in this case it's only for a few
layers at a time at most, so we are not experiencing any problems there.
I am wondering, in this blogpost:
http://themapguyde.blogspot.be/2013/08/mapguide-26-feature-showcase.html
It is mentioned that: "There are still unexplored caching opportunities on the
server side that could make these response times even faster!" could this be
related to the unexplored caching opportunities?
Cheers
[cid:[email protected]]
Ben Savelkoul
0494 64 63 73 |
[email protected]<mailto:[email protected]>
GEO Solutions nv, Prins Boudewijnlaan 41, 2650 Edegem
www.geosolutions.be<http://www.geosolutions.be/>
GIS op maat van uw organisatie |Advies | Analyse | Ontwikkeling | Data
From: Benoit Begin [via OSGeo.org]
[mailto:[email protected]]
Sent: dinsdag 28 februari 2017 21:07
To: Savelkoul Ben <[email protected]>
Subject: RE: 30 seconds delay after creating +/-100 CreateRuntimeMap calls
One thing to keep in mind is if you are batching all those calls to the
mapagent, you might be hitting the cap for simultaneously opened http requests
to the same server. It's a little bit different from browser to browser, but
typically only 4 to 8 http requests can be opened simultaneously to the same
server. So since creating a runtime map can be a little bit time consuming,
specially when creating so many at once, you might simply be stacking too many
queries.
You could work around the issue by creating all your runtime maps server-side
using php/.net and then just returning an array of all the map names you have
created. This could check if the issue is creating so many maps or if it's
because of too many http queries at once.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://osgeo-org.1560.x6.nabble.com/30-seconds-delay-after-creating-100-CreateRuntimeMap-calls-tp5309691p5309989.html
To unsubscribe from 30 seconds delay after creating +/-100 CreateRuntimeMap
calls, click
here<http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5309691&code=YmVuLlNhdmVsa291bEBnZW9zb2x1dGlvbnMuYmV8NTMwOTY5MXwtMTUyOTI0MTgxMQ==>.
NAML<http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
image001.png (6K)
<http://osgeo-org.1560.x6.nabble.com/attachment/5309997/0/image001.png>
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/30-seconds-delay-after-creating-100-CreateRuntimeMap-calls-tp5309691p5309997.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________
mapguide-users mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapguide-users
