Representation of repo rules in performance artifacts #22439
Labels
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
team-Performance
Issues for Performance teams
type: feature request
untriaged
Description of the feature request:
This feature request is about improving the representation of repo rules in Bazel's performance artifacts: trace profiles, exec logs, graph logs.
IIUC, currently the following limitations exist:
out
field populated in trace profiles (--experimental_profile_include_primary_output
);Having at least some of these fixed would be useful for projects like ChromeOS which have big repo rules (in our case, at the order of magnitude of 10 minutes). Currently we work it around by implementing the drag analysis ourselves after heuristically backfilling the missing edges to repo rules, but it'd be nice if these hacks weren't necessary in order to get unbiased performance analysis.
Which category does this issue belong to?
Core
What underlying problem are you trying to solve with this feature?
Better understanding of performance and bottlenecks in builds.
Which operating system are you running Bazel on?
Linux
What is the output of
bazel info release
?7.1.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: