Skip to content

QFastServer 3.44.15-qfs.1

Choose a tag to compare

@github-actions github-actions released this 11 Nov 18:43
· 7 commits to main since this release

First release of QFastServer for QGIS Server 3.44.15.

docker pull ghcr.io/envirosolutionspl/qfastserver:3.44.15-qfs.1

Use the image exactly as qgis/qgis-server:3.44.15-noble: same entry point, ports, volumes and environment
variables.

Compatibility

QGIS Server 3.44.15
Upstream tag and commit final-3_44_15, 44b4ef051784192d6e4829dc008bca120e4d2388
Patch series 3.44, 14 patches, fork commit d3c624ee6ec6c706cf6b48564ce12a289494370d
Base image qgis/qgis-server:3.44.15-noble
Qt 5.15

Verification

  • Responses compared with the official image qgis/qgis-server:3.44.15-noble: 56 of 59 request types
    identical. Not comparable, because they differ from run to run in the official image itself: 8 bits PNG,
    a cascaded WMS layer as PNG, PDF.
  • Raster renderings compared with an unpatched build: 68 of 68 identical.
  • Upstream tests (server, rasters, projects, vector layers, DXF): 139 of 139. They were run with the same
    patches on the branch release-3_44 28 commits after the tag final-3_44_15, not on the tag itself.
  • Upstream tests which need PostgreSQL: 36 of 39; the three failures do not depend on the patches (one is
    on the upstream blocklist, one needs a PostgreSQL binary which the test container does not have, one
    depends on the locale of the container).

Performance

The official image against this image, both started the same way (the nginx front of the image, 4 FastCGI
workers, parallel rendering off, 4 CPUs and 4 GB for the container, PostGIS 16 on the same host), k6, median
with one client and requests per second with 16 clients, no failed responses.

Request Median, 1 client Requests/s, 16 clients
Tile 256x256, 1 vector layer, PNG 10.9 → 4.5 ms 304 → 459
Tile 256x256, 3 vector layers, PNG 11.0 → 7.9 ms 222 → 271
Map 1024x768, 1 vector layer, PNG 30.3 → 18.0 ms 70 → 95
Map 1024x768, 3 vector layers, PNG 44.6 → 27.5 ms 42 → 57
Map 1024x768, raster in the layer CRS, JPEG 17.8 → 10.1 ms 198 → 301
Map 1024x768, raster reprojected, JPEG 37.5 → 18.9 ms 86 → 162
GetFeatureInfo, JSON 11.0 → 3.7 ms 374 → 871
GetLegendGraphic, PNG 10.9 → 4.5 ms 377 → 724
WMTS GetTile 10.9 → 5.3 ms 261 → 356
WFS GetFeature, GML 44.6 → 37.0 ms 57 → 74

Machine: Intel Core Ultra 7 165H (16 cores, 22 threads), 31 GB of memory, Docker Engine 29.9 on WSL 2.
The method and its limits are described in the README.

Changes

All 14 patches of the series; see UPSTREAM.md.

Known differences from upstream

  • PNG files of vector maps are smaller; PNG files of pure imagery are about 20% larger (rows are written
    without the filter search).
  • The image is built with the options of the upstream Debian packaging, without the desktop application and
    the GRASS plugins, which the official server image does not contain either.

Not verified

  • Python server plugins (for example lizmap_server) with this image.
  • WFS transactions, GetPrint with an atlas, GeoPDF.