Open offtherailz opened 7 years ago
Hi, has this issue been solved yet?
As far as I undrerstood this issue should be solved using a rule cache. @afabiani can you confirm ?
2017 to 2024 and still issue ! With a rdbms backend it's better but will not solve totally the performance impact
@kikislater any contribution is welcome!
You already implement it in Geonode as a docker receipt. Furthermore I have notice that remote services as a layer could slow down GetCapabilities requests in Geonode ... That's the major impact that could slow down geofence
With many roles for a user, rules readings becomes slow.
With a getCapabilities request and many layers the response takes too much to be generated (around 28 seconds with a user with 20 roles, 200 layers).
Probably the bottle-neck is here, but not sure:
https://github.com/geoserver/geofence/blob/master/src/services/core/services-impl/src/main/java/org/geoserver/geofence/services/RuleReaderServiceImpl.java#L500
We have
n_layers_published * n_roles_for_user
queries.i.e. 200 layer, 20 roles = 4000 queries