This repository was archived by the owner on Apr 2, 2026. It is now read-only.
Additional Tracing -for Perf Debugging#7
Merged
kumaramit01 merged 7 commits intofeatures/v2.6.6-patched-251123from Dec 6, 2025
Merged
Additional Tracing -for Perf Debugging#7kumaramit01 merged 7 commits intofeatures/v2.6.6-patched-251123from
kumaramit01 merged 7 commits intofeatures/v2.6.6-patched-251123from
Conversation
added 7 commits
December 4, 2025 22:29
Signed-off-by: Amit Kumar <[email protected]>
Signed-off-by: Amit Kumar <[email protected]>
Signed-off-by: Amit Kumar <[email protected]>
This reverts commit 36ac350.
This reverts commit 968ca56.
This reverts commit 716782d.
Signed-off-by: Amit Kumar <[email protected]>
04e4c7a
into
features/v2.6.6-patched-251123
9 of 14 checks passed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
💸 TL;DR
This PR adds a bunch more of tracing to debug performance bottleneck in Milvus. Expected trace for search

With all tracing enabled, a search request should show like this -We are seeing for non-failed queries search latencies > 1.5 sec
With a lot of time in schedule and segcore. The additional tracing would help us determine if the issue is with the
📜 Details
Design Doc
Jira
🧪 Testing Steps / Validation
✅ Checks