change profiling based partitoner's last_segment_latency to slowest_segment_latency #24
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.
Changed profile-based partitioner's
last_segment_latency
toslowest_segment_latency
.Actually it does not guarantee gap between slowest_segment_latency and fastest_segment_latency lower than
diff_threshold_ns
. But when using this code, I can see that the difference was reduced.I tried to use a different method, but I didn't converge.
And I tested by utilizing only one TPU. So I couldn't proceed with the experiment on more than 2 TPUs.
I'm using M.2 Accelerator with Dual Edge TPU, but I can't catch two TPUs... So my test can be inaccurate.