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
Describe the bug
The Time Counter tool in the Gremlin Service is responsible for calculating the execution time per query. However, due to recent changes introduced in the PR #2818, the behavior of the Time Counter has become inaccurate.
Previously, the compiler worker thread would wait for the response from the runtime and calculate the execution time, which was reasonable. However, after the mentioned PR was merged into the main branch, the worker thread no longer waits for the runtime response and sends the physical plan directly (grpc callback funtion will help to handle response). As a result, the execution time calculated by the Time Counter only reflects the compilation time, without accounting for the actual execution time by the runtime. This behavior is undesirable and needs to be addressed.
To Reproduce
Steps to reproduce the behavior:
Execute a query using the Gremlin Service.
Observe the reported execution time provided by the Time Counter.
Screenshots
Environment (please complete the following information):
GraphScope version: [main]
OS: [e.g. MacOS, Linux]
The text was updated successfully, but these errors were encountered:
<!--
Thanks for your contribution! please review
https://github.com/alibaba/GraphScope/blob/main/CONTRIBUTING.md before
opening an issue.
-->
## What do these changes do?
as titled
<!-- Please give a short brief about these changes. -->
## Related issue number
<!-- Are there any issues opened that will be resolved by merging this
change? -->
Fixes#2905
---------
Co-authored-by: Longbin Lai <[email protected]>
Describe the bug
The Time Counter tool in the Gremlin Service is responsible for calculating the execution time per query. However, due to recent changes introduced in the PR #2818, the behavior of the Time Counter has become inaccurate.
Previously, the compiler worker thread would wait for the response from the runtime and calculate the execution time, which was reasonable. However, after the mentioned PR was merged into the main branch, the worker thread no longer waits for the runtime response and sends the physical plan directly (grpc callback funtion will help to handle response). As a result, the execution time calculated by the Time Counter only reflects the compilation time, without accounting for the actual execution time by the runtime. This behavior is undesirable and needs to be addressed.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: