PVF: drop backing jobs if it is too late #5530
Assignees
Labels
I9-optimisation
An enhancement to provide better overall performance in terms of time-to-completion for a task.
Comments
sandreim
added
the
I9-optimisation
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 7, 2024
Fixes #5530 This PR introduces the removal of backing jobs that have been back pressured for longer than `allowedAncestryLen`, as these candidates are no longer viable. It is reasonable to expect a result for a backing job execution within `allowedAncestryLen` blocks. Therefore, we set the job TTL as a relay block number and synchronize the validation host by sending activated leaves. --------- Co-authored-by: Andrei Sandu <[email protected]> Co-authored-by: Branislav Kontur <[email protected]>
github-project-automation
bot
moved this from Backlog
to Completed
in parachains team board
paritytech-ci
pushed a commit
that referenced
this issue
Nov 7, 2024
Fixes #5530 This PR introduces the removal of backing jobs that have been back pressured for longer than `allowedAncestryLen`, as these candidates are no longer viable. It is reasonable to expect a result for a backing job execution within `allowedAncestryLen` blocks. Therefore, we set the job TTL as a relay block number and synchronize the validation host by sending activated leaves. --------- Co-authored-by: Andrei Sandu <[email protected]> Co-authored-by: Branislav Kontur <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #4632
If backing is being back pressured for longer than
allowedAncestryLen, it is pointless to execute these jobs as the candidate is no longer viable.We should pass a deadline timestamp for validation of backing jobs in the PVF host:
deadline = now() + allowedAncestryLen * 6 - PvfExecTimeout. Before executing backing jobs we should check if we are past the deadline and drop them.The text was updated successfully, but these errors were encountered: