You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Given a rank-profile with several phases, including an ONNX-inference with a crossencoder, for global phase-reranking.
I want to be able to analyze time spent on
The whole global-phase
Individual parts of the global-phase ranking.
When analyzing query trace with
"trace.level": 4,
"trace.timestamps": "true",
I can see the following jump in timestamps in the trace:
{
"timestamp": 10,
"message": "content.num0 dispatch response: Result (10 of total 1024 hits)"
},
{
"timestamp": 3255,
"message": "Return searcher 'com.yahoo.prelude.cluster.ClusterSearcher in content'"
},
Apparently, this step include the whole global-phase. That does not seem very obvious.
Describe the solution you'd like
It would be very nice to at least have a more descriptive message.
Even better if it were possible to get more granulated traces for different steps in rank-profile, that were linked to the expressions in the rank-profile, to be able to investigate performance more easily.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Given a rank-profile with several phases, including an ONNX-inference with a crossencoder, for global phase-reranking.
I want to be able to analyze time spent on
When analyzing query trace with
I can see the following jump in timestamps in the trace:
Apparently, this step include the whole global-phase. That does not seem very obvious.
Describe the solution you'd like
It would be very nice to at least have a more descriptive message.
Even better if it were possible to get more granulated traces for different steps in rank-profile, that were linked to the expressions in the rank-profile, to be able to investigate performance more easily.
The text was updated successfully, but these errors were encountered: