Performance scalability issues with Thumbnail generation #9637
Assignees
Labels
3.3.x
4.0.x
major
A high priority issue which might affect a lot of people or large parts of the codebase
master
performance
Issues regarding server Performance and Speed
Comments
afabiani
added
major
afabiani
added a commit
that referenced
this issue
Jul 11, 2022
12 tasks
afabiani
added a commit
that referenced
this issue
Jul 11, 2022
afabiani
added a commit
that referenced
this issue
Jul 11, 2022
#9638) (#9640) * [WIP] Direct GetMap request * [Fixes #9637] Performance scalability issues with Thumbnail generation * [Fixes #9637] Performance scalability issues with Thumbnail generation * [PEP-8] Fix syntax issues * - Fix test cases Co-authored-by: Alessio Fabiani <[email protected]>
Merged
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a Thumbnail, GeoNode actually performs a
WMS GetMap Requestagainst GeoServer.The issue with the former request is that before performing it GeoNose alwyas fetches the whole
GetCapabilitiesdocuemnt (see here).The
OWSLibconstructorwms = WebMapService(...)by default perform a fullGetCapabilitesrequest against the server.A severe issue with this approach is that this is not scalable, other than we already know the
layerswe want to fetch and therefore there's no need to perform an additional request.The proposed solution would be to perform the
GetMapstraight without parsing theGetCapabilitesdocument first.The text was updated successfully, but these errors were encountered: