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.
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
[flytepropeller][flyteadmin] Streaming Decks V2 #6053
[flytepropeller][flyteadmin] Streaming Decks V2 #6053
Changes from 3 commits
54aa165
9ed6b6e
4b4f6bd
dd774cb
0bb8e91
25fea29
4e24e91
8d1d0e4
31853bb
4068043
65b6efe
137579f
04f7fbc
aa56d64
a16851f
7314455
19498f5
74f595f
3bd3336
f6d8493
4b56e52
db4b19e
2737251
564dc5f
69ba94e
c992eae
0b91b5c
1d18265
96500c1
dd9dbaa
f51ff8c
bd5e682
561a43c
a33ba09
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 92 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L90-L92
Check warning on line 98 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L96-L98
Check warning on line 107 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L107
Check warning on line 110 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L110
Check warning on line 184 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L182-L184
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this do a
head
call on the deck URI for every task that succeeds? Two thoughts here:(1) does the flyteadmin merge algorithm then remove the deckURI from the execution metadata?
(2) this is incurring a 20-30ms performance degredation to every task execution
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will take a look tmr, thank you!!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it will do a
head
call byRemoteFileOutputReader
flyte/flyteplugins/go/tasks/pluginmachinery/ioutils/remote_file_output_reader.go
Lines 306 to 313 in b3330ba
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how do you know the performance degradation?
did you use grafana or other performance tools?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
flyteadmin will set the
deckURI
in theexecution metadata
tonil
if the propeller removes it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @hamersaw
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to just to close the loop on this, we're still making this HEAD call only when the node reaches the terminal phase.
Check warning on line 515 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L514-L515
Check warning on line 564 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L559-L564