-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sandboxing time breakdown in tracing profile needed #10404
Labels
team-Performance
Issues for Performance teams
Comments
meisterT
added a commit
to meisterT/bazel
that referenced
this issue
Dec 12, 2019
Fixes bazelbuild#10404. RELNOTES: None
@meisterT, I just got around to trying this... but I'm not sure what I should be seeing. I ran bazel as
|
I just realized that this just the Java object creation. I'll create a follow-up commit... |
meisterT
added a commit
to meisterT/bazel
that referenced
this issue
Dec 17, 2019
The previous attempt only accounted for the object creation but not the actual sandbox setup. Fix bazelbuild#10404. RELNOTES: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed at BazelCon, debugging the sandbox performance problem on macOS would be easier if there was an option to add to the trace profile a break down, per action, of the time it takes to set up the sandbox, the time it takes to execute the action’s command, and the time it takes to tear down the sandbox.
The text was updated successfully, but these errors were encountered: