Task #10071
closed
test a varnish cache before the PAIM geoservers
100%
Description
Try on geoserver1-paim first. If it does advantages, install it on geoserver2-paim too.
Related issues
Updated by Andrea Dell'Amico over 7 years ago
- Related to VM Creation #10069: VM for geowebcache testing under PAIM added
Updated by Andrea Dell'Amico over 7 years ago
- Status changed from New to In Progress
Updated by Andrea Dell'Amico over 7 years ago
We are going to give a shot to https://mapproxy.org instead
Updated by Andrea Dell'Amico over 7 years ago
- % Done changed from 0 to 30
mapproxy has a questionable documentation. There's a tool to autoconfigure services and layers, but when run against the paim geoserver it creates a configuration that does not validate:
KeyError: 'W_mpa'
I removed all the W_mpa: prefixes the it didn't like and I was then able to start the service. But it's not transparent.
It seems very powerful but it also needs a very carefully planned configuration. It could be very useful in the long term, but not something to set up hastly. I'll go back to varnish to see if it can help somewhat (the mapproxy documentation lists varnish as one of the recommended frontends, btw).
Updated by Andrea Dell'Amico over 7 years ago
- % Done changed from 30 to 80
Both geoserver1-protectedareaimpactmaps.d4science.org and geoserver2-protectedareaimpactmaps.d4science.org are under a varnish instance right now.
One varnish instance for each geoserver, running locally. The flow is now:
haproxy -> nginx -> varnish -> geoserver
nginx was manually reconfigured, some work will be needed to integrate varnish completely.
Updated by Andrea Dell'Amico over 7 years ago
- Related to Task #10147: Support varnish as a cache layer in the smartgears nginx added
Updated by Andrea Dell'Amico over 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 80 to 100
