Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Set DexBuilder to use persistent workers by default #5771

Closed
jin opened this issue Aug 5, 2018 · 0 comments
Closed

Set DexBuilder to use persistent workers by default #5771

jin opened this issue Aug 5, 2018 · 0 comments
Assignees
@jin
Labels
P2 We'll consider working on this in future. (Assignee optional) team-Android Issues for Android team type: feature request

Comments

@jin
Copy link
Member

jin commented Aug 5, 2018

With --strategy=DexBuilder=worker, we see ~1.2x speedup on clean local Android builds.
@jin jin self-assigned this Aug 5, 2018
@jin jin added P2 We'll consider working on this in future. (Assignee optional) team-Android Issues for Android team labels Aug 5, 2018
luca-digrazia pushed a commit to luca-digrazia/DatasetCommitsDiffSearch that referenced this issue Sep 4, 2022
Set the default strategy of DexBuilder to use persistent workers.
3186933 
    This brings 1.2x speedup to clean local Android builds.

    Fixes bazelbuild/bazel#5771

    RELNOTES: For Android incremental dexing actions, Bazel now persists its DexBuilder process across individual actions. From our benchmarks, this results in a 1.2x speedup for clean local builds.
    PiperOrigin-RevId: 208546936
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jin jin

Labels
P2 We'll consider working on this in future. (Assignee optional) team-Android Issues for Android team type: feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jin