Repository navigation
Skill references: describe null MXU and compute_efficiency_percent - #4086
Open
copybara-service[bot] wants to merge 1 commit into
Open
copybara-service[bot] wants to merge 1 commit into
copybara-service[bot] wants to merge 1 commit into
Conversation
The get_overview and get_kpi_metrics references now say that mxu_utilization_percent comes from hardware performance counters and is null when the capture has no counters. In that case mxu_utilization_status gives the reason and a way to get the value. The references also describe compute_efficiency_percent, a FLOP rate estimate from the XLA cost model. A new "Missing Hardware Counters" section in the get_overview reference tells the agent to report MXU utilization as unknown, not 0%. It also tells the agent to use compute_efficiency_percent as a cost-model estimate, to try get_kernel_utilization, and to capture the profile again with counters. PiperOrigin-RevId: 1021022701
copybara-service
Bot
force-pushed
the
test_1021022701
branch
from
November 14, 2026 02:50
672a48b to
e52a936
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Skill references: describe null MXU and compute_efficiency_percent
The get_overview and get_kpi_metrics references now say that
mxu_utilization_percent comes from hardware performance counters and is null
when the capture has no counters. In that case mxu_utilization_status gives the
reason and a way to get the value.
The references also describe compute_efficiency_percent, a FLOP rate estimate
from the XLA cost model. A new "Missing Hardware Counters" section in the
get_overview reference tells the agent to report MXU utilization as unknown,
not 0%. It also tells the agent to use compute_efficiency_percent as a
cost-model estimate, to try get_kernel_utilization, and to capture the profile
again with counters.