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

[Backport 8.x] benchmark script #17283

Merged
merged 7 commits into from
Mar 7, 2025

Conversation

kaisecheng
Copy link
Contributor

@kaisecheng kaisecheng commented Mar 6, 2025

A couple of benchmark script PRs didn't backport to 8.x
This commit cherry-pick the missing PRs to one

[CI] benchmark uses the new artifacts-api (#17224)
[CI] benchmark readme (#16783)
Introduce a new flag to explicitly permit legacy monitoring (#16586) (Only take the benchmark script)
[ci] fix wrong queue type in benchmark marathon (#16465)
[CI] fix benchmark marathon (#16447)
[CI] benchmark dashboard and pipeline for testing against multiple versions (#16421)

kaisecheng and others added 6 commits March 6, 2025 16:32
…rsions (elastic#16421)

- add becnhmark dashboard and related save objects
- add one buildkite pipeline to test against multiple versions
- remove null field in json
- add `FLOG_FILE_CNT`, `VAULT_PATH`, `TAGS`
- split main.sh to core.sh and main.sh
- rename all.sh to marathon.sh
- fix vault expiry issue for long running task
- fix unable to call main function
- update save object runtime field `release` to return true when `version` contains "SNAPSHOT"
- add instruction to run benchmark in v8 with `xpack.monitoring.allow_legacy_collection`
- remove scripted field 5m_num from dashboards
migrate benchmark to the new artifacts-api
Introduce a new flag to explicitly permit legacy monitoring (elastic#16586)
@@ -3,6 +3,7 @@ pipeline.workers: ${WORKER}
pipeline.batch.size: ${BATCH_SIZE}
queue.type: ${QTYPE}

xpack.monitoring.allow_legacy_collection: true
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the unclean backport of #16586

Copy link
Contributor

@mashhurs mashhurs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Note that this PR doesn't have any functionality effect.
I understand that in 8.x (or other branches) may contain unnecessary/confusing codes/endpoints (for example artifact API), so this backport doesn't hurt. The only thing I would ask is not to change catalog-info.yaml to keep CIs safe with CI build systems.

@kaisecheng kaisecheng merged commit 4fd1373 into elastic:8.x Mar 7, 2025
4 of 5 checks passed
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

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 this pull request may close these issues.

3 participants