Skip to content

early linting: avoid redundant calls to check_id #142398

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fee1-dead
Copy link
Member

An attempt to address the regression at #142240 (comment)

r? @oli-obk

cc @nnethercote who might have a better understanding of the performance implications

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jun 12, 2025
@fee1-dead fee1-dead force-pushed the push-ynxrtswtkyxw branch from 51736c3 to ac92e87 Compare June 12, 2025 06:03
@fee1-dead
Copy link
Member Author

@bors try @rust-timer queue

@rust-timer

This comment has been minimized.

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Jun 12, 2025
@fee1-dead fee1-dead changed the title early linting: avoiding redundant calls to check_id early linting: avoid redundant calls to check_id Jun 12, 2025
bors added a commit that referenced this pull request Jun 12, 2025
early linting: avoid redundant calls to `check_id`

An attempt to address the regression at #142240 (comment)

r? `@oli-obk`

cc `@nnethercote` who might have a better understanding of the performance implications
@bors
Copy link
Collaborator

bors commented Jun 12, 2025

⌛ Trying commit ac92e87 with merge 73e31b9...

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented Jun 12, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 12, 2025
@oli-obk
Copy link
Contributor

oli-obk commented Jun 12, 2025

Sad. Would need to revert #142305, too then. At this point it may be prudent to remove visit_id entirely as it's a footgun

@fee1-dead
Copy link
Member Author

it might still be possible to keep using visit_id, I just haven't looked into it deeply yet. After removing the redundant calls we can do some perf measurements. If it still is bad then we should revert to previous state.

@fee1-dead fee1-dead force-pushed the push-ynxrtswtkyxw branch from ac92e87 to ae8ca1f Compare June 12, 2025 11:01
@fee1-dead
Copy link
Member Author

@bors try @rust-timer queue

@rust-timer

This comment has been minimized.

bors added a commit that referenced this pull request Jun 12, 2025
early linting: avoid redundant calls to `check_id`

An attempt to address the regression at #142240 (comment)

r? `@oli-obk`

cc `@nnethercote` who might have a better understanding of the performance implications
@bors
Copy link
Collaborator

bors commented Jun 12, 2025

⌛ Trying commit ae8ca1f with merge 9fe6114...

@bors
Copy link
Collaborator

bors commented Jun 12, 2025

☀️ Try build successful - checks-actions
Build commit: 9fe6114 (9fe61147dc9031465e04140f03586e3d72f36e6c)

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (9fe6114): comparison URL.

Overall result: ✅ improvements - no action needed

Benchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf.

@bors rollup=never
@rustbot label: -S-waiting-on-perf -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.3% [-0.6%, -0.1%] 30
Improvements ✅
(secondary)
-0.4% [-1.0%, -0.0%] 36
All ❌✅ (primary) -0.3% [-0.6%, -0.1%] 30

Max RSS (memory usage)

Results (primary 0.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
1.3% [1.2%, 1.4%] 2
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.5% [-1.5%, -1.5%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.4% [-1.5%, 1.4%] 3

Cycles

Results (secondary -7.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-7.0% [-7.0%, -7.0%] 1
All ❌✅ (primary) - - 0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 755.158s -> 754.58s (-0.08%)
Artifact size: 372.13 MiB -> 372.08 MiB (-0.01%)

@rustbot rustbot removed the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Jun 12, 2025
@oli-obk
Copy link
Contributor

oli-obk commented Jun 12, 2025

@bors r+ yay

@bors
Copy link
Collaborator

bors commented Jun 12, 2025

📌 Commit ae8ca1f has been approved by oli-obk

It is now in the queue for this repository.

@bors bors removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jun 12, 2025
@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants