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

FieldConfigHelper results cache #2612

Open
dtspence opened this issue Oct 16, 2024 · 0 comments · May be fixed by #2614
Open

FieldConfigHelper results cache #2612

dtspence opened this issue Oct 16, 2024 · 0 comments · May be fixed by #2614
Assignees

Comments

@dtspence
Copy link
Collaborator

dtspence commented Oct 16, 2024

JFR analysis showed there may be a cost with pattern evaluation in the FieldConfigHelper. In testing/benchmarks, it appears that caching the field lookup results would help with ingest performance.

Evaluate optionally including a cache that can be configured to keep results of field evaluations. The implementation should also be aware of some configurable maximum limit.

@dtspence dtspence self-assigned this Oct 16, 2024
@dtspence dtspence linked a pull request Oct 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant