[performance] add 8000 fields to dashboard journeys#248525
Merged
drewdaemon merged 5 commits intoelastic:mainfrom Jan 20, 2026
Merged
[performance] add 8000 fields to dashboard journeys#248525drewdaemon merged 5 commits intoelastic:mainfrom
drewdaemon merged 5 commits intoelastic:mainfrom
Conversation
drewdaemon
added
release_note:skip
drewdaemon
changed the title
dmlemeshko
approved these changes
Jan 12, 2026
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
|
merge conflict between base and head |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
|
dennis-tismenko
pushed a commit
to dennis-tismenko/kibana
that referenced
this pull request
Jan 22, 2026
## Summary Right now these journey datasets have less than 100 fields. Instead, we want a number that is challenging to our performance but still realistic. We want to see signals that we are improving when we make changes to field list loading, but not an unreasonable signal. 8000 fields is large enough to give us a signal, but not so large that we would say "don't do this." --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Right now these journey datasets have less than 100 fields. Instead, we want a number that is challenging to our performance but still realistic. We want to see signals that we are improving when we make changes to field list loading, but not an unreasonable signal.
8000 fields is large enough to give us a signal, but not so large that we would say "don't do this."