Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systematically distinguish accumulated parallel time from walltime #56746

Closed
Tracked by #56232
yibin87 opened this issue Oct 21, 2024 · 0 comments · Fixed by #57507
Closed
Tracked by #56232

Systematically distinguish accumulated parallel time from walltime #56746

yibin87 opened this issue Oct 21, 2024 · 0 comments · Fixed by #57507
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@yibin87
Copy link
Contributor

yibin87 commented Oct 21, 2024

Enhancement

Currently, the "time" field in execution info may represent the execution time of a specific executor or the total execution time of multiple "cloned" executors which are executed parallely, such as ParallelApply cases:
image

This situation is very confusing, since the Limit_17 operator's time is much more than its parent operator's time. So it is necessary to distinguish between these two meanings. At the same time, it is best to have a systematic and unified method to avoid processing each operator independently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant