Skip to content

so_vector - Add ES|QL queries profiling#973

Merged
carlosdelest merged 28 commits intoelastic:masterfrom
carlosdelest:enhancement/so_vector-esql-profiling
Dec 18, 2025
Merged

so_vector - Add ES|QL queries profiling#973
carlosdelest merged 28 commits intoelastic:masterfrom
carlosdelest:enhancement/so_vector-esql-profiling

Conversation

@carlosdelest
Copy link
Member

Adds ES|QL profiling metrics to the following ES|QL queries:

  • esql-profile-knn-search-default-match-all
  • esql-profile-knn-search-100-300-match-all
  • esql-profile-script-score-query-match-all

The goal is to have a minimum set of different queries that gathers profile information so it can be analyzed in terms of time spent on the different phases.

The following metrics are retrieved from ES|QL profile and included into rally metrics:

  • meta.query.took_ms: Total query time took
  • meta.planning.took_ms: Planning time before query execution, includes parsing, preanalysis, analysis
  • meta.parsing.took_ms: Time it took to parse the ESQL query
  • meta.preanalysis.took_ms: Preanalysis, including field_caps, enrich policies, lookup indices
  • meta.analysis.took_ms: Analysis time before optimizations
  • meta..cpu_ms: Total plan CPU time
  • meta..took_ms: Total plan took time
  • meta..logical_optimization.took_ms: Plan logical optimization took time
  • meta..physical_optimization.took_ms: Plan physical optimization took time
  • meta..reduction.took_ms: : Node reduction plan generation took time
  • meta...process_ms: Processing time for each operator in the plan

See elastic/elasticsearch#139540 and elastic/elasticsearch#138564

@carlosdelest carlosdelest merged commit 7a943ea into elastic:master Dec 18, 2025
15 checks passed
@esbenchmachine
Copy link
Collaborator

💚 All backports created successfully

Status Branch Result
9.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

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

3 participants