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.
Closes #15391
In #14651 we started tracking task run states with a
WeakValueDictionary
to avoid memory bloat in flow with many tasks. Using aWeakValueDictionary
can lead task run states to be garbage collected too soon which remove the information necessary to consistently show data dependencies between tasks.This PR goes back to using a
dict
to track task run states, but drops the return value from the user's code to avoid memory bloat.Using the following script, we can see that memory usage stays roughly consistent (or even improves a bit) before and after this change:
Here are the results:
Before
n=100 w/ WeakValueDictionary
n=1000 w/ WeakValueDictionary
After
n=100 w/ dict
n=1000 w/ dict
Alternatives considered
I explored using
weakref.finalizer
to try to intelligently remove tracked task run states when the associate return value is garbage collection, but weak references cannot be created for all objects (likeint
orstr
) so unfortunately, that approach didn't work.