Feature Wiki
Tabs
Use GlobalCache for Logging-Settings
Page Overview
[Hide]1 Initial Problem
The settings for the log components and the log levels per component are stored in the database. This information is needed for every request and is one of the top queries on the database for many installations (measured by the total time needed for the query). The query in SQL is very good and performant, but due to the amount of queries needed, this adds up to a top query.
2 Conceptual Summary
We suggest that the settings are cached when GlobalCache is activated. This eliminates the need for many queries on the database until something changes in the settings.
We suggest that if no cache service (such as APC or Memcached) is activated, the data is still stored in PHP Static Adapter, which probably eliminates some queries.
3 User Interface Modifications
3.1 List of Affected Views
- none
3.2 User Interface Details
None
3.3 New User Interface Concepts
None
3.4 Accessibility Implications
None, no changes in the User Interface
4 Technical Information
The implementation uses the new caching service under src/GlobalCache. This container must then be flushed each time settings are changed in the administration.
5 Privacy
No (new) user-related data is collected, processed or stored in this feature.
6 Security
No new attack vectors are introduced with this feature. The loggin service must obtain the data from the cache via the refinery/transformations.
7 Contact
- Author of the Request: Schmid, Fabian [fschmid]
- Maintainer: Meyer, Stefan [smeyer]
- Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}
8 Funding
If you are interest in funding this feature, please add your name and institution to this list.
- …
9 Discussion
10 Implementation
{ The maintainer has to give a description of the final implementation and add screenshots if possible. }
Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
Privacy
Information in privacy.md of component: updated on {date} by {user} | no change required
Approval
Approved at {date} by {user}.
Last edited: 24. Apr 2023, 10:50, Schmid, Fabian [fschmid]