You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jörg Hoh (Jira)" <ji...@apache.org> on 2021/01/30 15:44:00 UTC
[jira] [Created] (SLING-10107) Refactoring of creation of
ResourceResolvers
Jörg Hoh created SLING-10107:
--------------------------------
Summary: Refactoring of creation of ResourceResolvers
Key: SLING-10107
URL: https://issues.apache.org/jira/browse/SLING-10107
Project: Sling
Issue Type: Improvement
Components: Content Distribution
Affects Versions: Content Distribution Journal Core 0.1.16
Reporter: Jörg Hoh
In the 2 classes {{Bookkepper}} and the {{Localstore}} the creation of ResourceResolvers is spread over multiple places, and also the number of methods, where ResourceResolvers are opened for obviously tiny operations is quite high.
Therefor I refactored the creation of ResourceResolvers for the subservice bookkeeper (which is the majority of cases) and centralized the creation of it into a central supplier within the {{Bookkeeper}}. I also added a new Gauge metric to observe how often a new ResourceResolver is actually created.
My gut feeling is, that the number of creations is (too) high; but before I start combining operations and reduce the number of ResourceResolver creations, I would like to understand if it's a problem at all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)