Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of caching functionality to the GenericAdder #534

Open
Malutthias opened this issue Mar 4, 2024 · 1 comment
Open

Addition of caching functionality to the GenericAdder #534

Malutthias opened this issue Mar 4, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Malutthias
Copy link
Collaborator

Malutthias commented Mar 4, 2024

We advocate for the integration of a caching feature into the GenericAdder to address a crucial requirement. This need arises due to the preprocessor's frequent database checks for updates. Presently, these connections are sequentially established within each Logprep instance.

The rationale behind this proposal stems from the potential expansion of fields within such rules. Without caching, this growth could overwhelm the database. Furthermore, retaining open connections to the database might seem viable, but it would lead to a substantial surge in the number of connections, potentially up to 10-15 times per field.

@Malutthias Malutthias added the enhancement New feature or request label Mar 4, 2024
@ekneg54
Copy link
Collaborator

ekneg54 commented Mar 4, 2024

I suggest to hide your database behind an API and drop the MySQL Feature from the generic adder. Instead you could use the config refresh mechanic in combination with a list from URL as supportet for all lists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants