Skip to content
This repository was archived by the owner on Oct 14, 2025. It is now read-only.

change profiling based partitoner's last_segment_latency to slowest_segment_latency#24

Open
HanChangHun wants to merge 1 commit intogoogle-coral:masterfrom
HanChangHun:master
Open

change profiling based partitoner's last_segment_latency to slowest_segment_latency#24
HanChangHun wants to merge 1 commit intogoogle-coral:masterfrom
HanChangHun:master

Conversation

@HanChangHun
Copy link
Copy Markdown

Changed profile-based partitioner's last_segment_latency to slowest_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.

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Jun 6, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant