08-25, 11:30–12:00 (Europe/Rome), Room Onice
With our Lizmap hosting service, we provide and monitor several hundred of QGIS servers. These QGIS Servers receive and process 3.5 million requests per week, including 3 million WMS GetMap requests.
We do not control the content of these QGIS projects, which are sent by our customers on our servers. Therefore, we need to deal with projects having some various kind of issues. Some QGIS projects can have very heavy SQL views which are slow to load. Our infrastructure may host projects having hundreds of layers with complex symbology. Users can publish QGIS PDF layouts (A4 and A3) with custom logos etc. This can lead to memory problems.
GIS technicians can add different data sources : vector and raster files, PostgreSQL / PostGIS database, OGC WMS, WFS and WMTS web services into these QGIS projects. We need to ensure that QGIS Server is working properly, for all customers, to execute incoming requests when some external Web Services providers are too slow to respond or are temporarily offline.
We need to take care of possible errors propagated by these projects. In some circumstances, we have about 10 thousand errors per week coming from QGIS server.
The goal of this presentation is to give an overview of what QGIS Server can experience into the wild and what we need to do to make the Lizmap user experience the best possible: monitoring, proxy, caching.
OpenSource GIS enthusiast since 2005
Love QGIS & PostgreSQL
Contribute to Lizmap Web Client, QGIS scripts and plugins
Work in 3liz, France
For 15 years, I have been working with OSGeo software. I co-founded 3Liz in 2007 to provide services on OSGeo software. In 2011, with Michaël DOUCHIN, we launched Lizmap. I am also QGIS core developer and QGIS Server maintainer.