<div dir="ltr"><div><div><div><div><div><div><div>100 layers are not really many.<br><br></div>As example: you can think to our Land-Usability wms.<br></div>It return evenry single code as a layer.<br></div><div>And also grouped layers.<br>
</div>And we have 2 year (2007 and 2010) in the same wms service.<br><br> <a href="http://www502.regione.toscana.it/wmsraster/com.rt.wms.RTmap/wms?map=wmsucs&service=wms&request=GetCapabilities">http://www502.regione.toscana.it/wmsraster/com.rt.wms.RTmap/wms?map=wmsucs&service=wms&request=GetCapabilities</a><br>
<br></div>It is just now more then 100 layers.<br><br></div><div>Actually it is served with a Mapserverand 1 only spatialite that host all the dataset.<br>I guess actually it was impossible to server with a QGIS-Server.<br>
<br></div><div>I don't understand why the qgis-server eed to calculate always the bbox.<br>In the server project windows, <br>qgis ask for the published bbox.<br></div><div>Why it don't use it as bbox rather than calculate it on every request ?<br>
<br></div><div>The FastCGI don't help really.<br>In a publishing environment every few hour the instances are restated to removed zombi process.<br>This mean that every few hours the FastCGI are emptied and reloaded.<br>
A fastcgi environment mean to load 20 instances of QGIS-server and every of them do them own elaboration .<br>As the bbox calculation for every layer.<br><br>GASP.<br>The start could ask about one hours and more.<br></div>
<br></div>Also another problem with the fastcig is that when <br></div><div>I change something on a project I need to restart to Web instances to dismiss the actual project and reload the new.<br><br></div><div>So every change in a qgis project need a restart of all proccess (20 and so on in a fastcgi enviroment) every with a slow bbox calculation phase.<br>
<br></div><div>mmhh...<br><br></div><div>:/<br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-14 9:13 GMT+01:00 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"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-14 Marco Hugentobler <span dir="ltr"><<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a>></span>:<div class="">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Andrea<div><br>
<br>
>I suspect that QS try always to recalc the box of every layer.<br>
<br></div>
QGIS server caches layers (up to 100, but that can be enhanced
using the environment variable MAX_CACHE_LAYERS). Furthermore,
the GetCapabilities documents are cached (so no recalculation if
using FastCGI).<div><br></div></div></div></blockquote><div><br></div></div><div>Thanks Marco, you confirmed what I told Andrea.</div><div>It would be a good enhancement if caching could be done in a persitent manner (out of memory). We could consider, in the future, to use memcache or something similar.</div>
<div><br></div><div>giovanni</div></div>
</div></div>
<br>_______________________________________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br></blockquote></div><br><br clear="all"><br>-- <br>-----------------<br>Andrea Peri<br>. . . . . . . . . <br>
qwerty àèìòù<br>-----------------<br>
</div>