Skip to content

Conversation

@andrevandeven
Copy link
Contributor

@andrevandeven andrevandeven commented Jul 1, 2025

The design will mimic that of query profiling but with a variation in the profile tree. The fetch profile tree will always contain a single root node that contains the following information:

  • Time spent creating the stored fields visitor
  • Time spent building fetch sub-phase processors
  • Time spent switching to the next segment
  • Time spent loading stored fields for a hit
  • Time spent loading the document _source

The tree will also contain a child node for each fetch sub-phase that runs (see appendix for a list of all sub-phases). The child node breakdown will contain the following information:

  • Time spent switching to the next segment
  • Time spent executing a fetch sub-phase
Image

Note: the above diagram only shows sub-phases for simplicity.

Related Issues

Resolves #1764

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@github-actions github-actions bot added distributed framework enhancement Enhancement or improvement to existing feature or request lucene labels Jul 1, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2025

❌ Gradle check result for 30e991d: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@msfroh
Copy link
Contributor

msfroh commented Jul 1, 2025

Ooh, neat! I'll review this week, but in case I forget, please feel free to @ mention me, @andrevandeven.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 2, 2025

❌ Gradle check result for 82d47ef: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 2, 2025

❌ Gradle check result for 9c9a819: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 3, 2025

❌ Gradle check result for 582046a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 7, 2025

❌ Gradle check result for 9304305: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2025

❌ Gradle check result for bad98f0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2025

❌ Gradle check result for bf5672e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2025

❌ Gradle check result for 3ee163b: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2025

❌ Gradle check result for 615fe3d:

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2025

❌ Gradle check result for 09b4bf0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2025

❌ Gradle check result for fde8d04: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2025

❌ Gradle check result for efbfcfc: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2025

❌ Gradle check result for b1a271e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2025

❌ Gradle check result for 980f63d: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2025

❌ Gradle check result for 13a1a98: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Andre van de Ven and others added 4 commits July 9, 2025 09:39
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
@github-actions
Copy link
Contributor

❌ Gradle check result for bdc5fc9: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

…r next_reader

Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
@github-actions
Copy link
Contributor

❌ Gradle check result for d03e2e7: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
@github-actions
Copy link
Contributor

❌ Gradle check result for 6683ccc: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
@andrevandeven andrevandeven requested a review from msfroh July 31, 2025 17:38
@andrevandeven
Copy link
Contributor Author

@msfroh I've decided to create a META issue to break this into smaller changes. I've disabled profiling of InnerHits and TopHitsAggregation for now, but have documented them in an issue within the Meta. Would appreciate if you could review again!

@github-actions
Copy link
Contributor

✅ Gradle check result for cf75be8: SUCCESS

Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
@msfroh
Copy link
Contributor

msfroh commented Jul 31, 2025

@msfroh I've decided to create a META issue to break this into smaller changes. I've disabled profiling of InnerHits and TopHitsAggregation for now, but have documented them in an issue within the Meta. Would appreciate if you could review again!

Yeah, that makes sense! They're complicated special cases, so punting them to their own task sounds right. 👍

@github-actions
Copy link
Contributor

✅ Gradle check result for f6d05d4: SUCCESS

@andrevandeven
Copy link
Contributor Author

@msfroh Thanks for the review! I've resolved remaining comments, so should be good to go.

Copy link
Contributor

@jainankitk jainankitk left a comment

Choose a reason for hiding this comment

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

Thanks @andrevandeven for this useful contribution!

@jainankitk jainankitk merged commit e082c30 into opensearch-project:main Jul 31, 2025
31 checks passed
sunqijun1 pushed a commit to sunqijun1/OpenSearch that referenced this pull request Aug 4, 2025
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <113951599+andrevandeven@users.noreply.github.com>
Co-authored-by: Andre van de Ven <andrevdv@amazon.com>
Signed-off-by: sunqijun.jun <sunqijun.jun@bytedance.com>
tandonks pushed a commit to tandonks/OpenSearch that referenced this pull request Aug 5, 2025
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <113951599+andrevandeven@users.noreply.github.com>
Co-authored-by: Andre van de Ven <andrevdv@amazon.com>
vinaykpud pushed a commit to vinaykpud/OpenSearch that referenced this pull request Sep 26, 2025
Signed-off-by: Andre van de Ven <andrebvandeven@gmail.com>
Signed-off-by: Andre van de Ven <113951599+andrevandeven@users.noreply.github.com>
Co-authored-by: Andre van de Ven <andrevdv@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

distributed framework documentation pending Tracks issues which have PRs merged but documentation changes pending enhancement Enhancement or improvement to existing feature or request lucene

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add fetch phase to search profile

5 participants