Skip to content

Add centroid benchmarks for geoshape#1091

Merged
craigtaverner merged 5 commits intoelastic:masterfrom
craigtaverner:geooshape_centroid
Mar 18, 2026
Merged

Add centroid benchmarks for geoshape#1091
craigtaverner merged 5 commits intoelastic:masterfrom
craigtaverner:geooshape_centroid

Conversation

@craigtaverner
Copy link
Contributor

@craigtaverner craigtaverner commented Mar 17, 2026

We already have centroid benchmarks for both QueryDSL and ES|QL over geo_point in the geopoint track. This PR adds similar benchmarks for the geoshape track, since Elasticsearch ES|QL recently got support for geo_shape in ST_CENTROID_AGG.

Centroid / bounds benchmark results (geoshape)

Tasks containing centroid or bounds. Latency = 50th percentile (ms). Empty cell = no result for that variant.

centroid bounds filter QueryDSL (ms) ESQL (ms)
X 831.06 507.18
X X 2516.20 731.06
X 1242.26 457.93
X X 145.26 106.82
X X X 385.14 142.79
X X 173.66 97.45

(filter = polygon in task name)

@craigtaverner craigtaverner requested a review from iverase March 17, 2026 16:12
@craigtaverner craigtaverner merged commit 102b556 into elastic:master Mar 18, 2026
15 checks passed
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Mar 18, 2026
@esbenchmachine
Copy link
Collaborator

@craigtaverner
A backport is pending for this PR.
Apply all the labels that correspond to Elasticsearch minor versions expected to work with this PR, but select only from the available ones.
If intended for future releases, apply label for next minor

When a vX.Y label is added, a new pull request will be automatically created, unless merge conflicts are detected or if the label supplied points to the next Elasticsearch minor version. If successful, a link to the newly opened backport PR will be provided in a comment.

In case of merge conflicts during backporting, create the backport PR manually following the steps from README:
Final steps to complete the backporting process:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure each backport pull request is labeled with backport.
  3. Review and merge each backport pull request into the appropriate version branch.
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants