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.

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

Attempt to make main repo mapping inverse more efficient #20617

Closed
wants to merge 1 commit into from

Conversation

Wyverald
Copy link
Member

Fixes #20613

@github-actions github-actions bot added the awaiting-review PR is awaiting review from an assigned reviewer label Dec 19, 2023
@Wyverald
Copy link
Member Author

Not completely sold on this, btw. But it's the path of least resistance (regarding code changes).

@Wyverald
Copy link
Member Author

cc @JohnRambo

During `bazel query`, `Label#getDisplayForm(mainRepoMapping)` might be called many many times. We can optimize for that case without sacrificing too much memory by computing a reverse mapping for the main repo mapping only.

Fixes #20613.

Closes #20617.

PiperOrigin-RevId: 592297440
Change-Id: Iaaa709a51fe39556f03408080c1fe5e73689b761
@JohnRambo
Copy link

Thanks @Wyverald for a quick fix.

FWIW I built bazel from your branch and confirmed this works on our repo.

@iancha1992 iancha1992 added the team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. label Dec 20, 2023
@Wyverald Wyverald added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Dec 20, 2023
@github-actions github-actions bot removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Dec 20, 2023
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request Dec 20, 2023
During `bazel query`, `Label#getDisplayForm(mainRepoMapping)` might be called many many times. We can optimize for that case without sacrificing too much memory by computing a reverse mapping for the main repo mapping only.

Fixes bazelbuild#20613.

Closes bazelbuild#20617.

PiperOrigin-RevId: 592607904
Change-Id: Iaaa709a51fe39556f03408080c1fe5e73689b761
@Wyverald Wyverald deleted the wyv-repo-mapping-inverse branch December 20, 2023 19:12
Wyverald added a commit that referenced this pull request Dec 20, 2023
)

During `bazel query`, `Label#getDisplayForm(mainRepoMapping)` might be
called many many times. We can optimize for that case without
sacrificing too much memory by computing a reverse mapping for the main
repo mapping only.

Fixes #20613.

Closes #20617.

Commit
d9169ab

PiperOrigin-RevId: 592607904
Change-Id: Iaaa709a51fe39556f03408080c1fe5e73689b761

Co-authored-by: Googler <wyv@google.com>
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request Dec 21, 2023
During `bazel query`, `Label#getDisplayForm(mainRepoMapping)` might be called many many times. We can optimize for that case without sacrificing too much memory by computing a reverse mapping for the main repo mapping only.

Fixes bazelbuild#20613.

Closes bazelbuild#20617.

PiperOrigin-RevId: 592607904
Change-Id: Iaaa709a51fe39556f03408080c1fe5e73689b761
github-merge-queue bot pushed a commit that referenced this pull request Jan 4, 2024
)

During `bazel query`, `Label#getDisplayForm(mainRepoMapping)` might be
called many many times. We can optimize for that case without
sacrificing too much memory by computing a reverse mapping for the main
repo mapping only.

Fixes #20613.

Closes #20617.

Commit
d9169ab

PiperOrigin-RevId: 592607904
Change-Id: Iaaa709a51fe39556f03408080c1fe5e73689b761

Co-authored-by: Googler <wyv@google.com>
Co-authored-by: Ian (Hee) Cha <heec@google.com>
Co-authored-by: Xùdōng Yáng <wyverald@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bazel query --output streamed_proto regression in 7.0.0
4 participants