-
Notifications
You must be signed in to change notification settings - Fork 13.8k
(EXPERIMENT) Perf experiments for target-machine command-line quoting #146804
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
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
(EXPERIMENT) Perform target-machine command-line quoting as bytes, not characters
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (515de9c): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking 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 Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 470.599s -> 471.807s (0.26%) |
ecc590c
to
df5de03
Compare
I'm going to recycle this PR for a few related perf experiments. Ironically, benchmarking these changes is only possible because we prepare quoted command-line arguments for all targets, even though the string only gets used for generating PDBs. @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
(EXPERIMENT) Perf experiments for target-machine command-line quoting
This comment has been minimized.
This comment has been minimized.
There's a more general problem that producing this command-line string makes It would be nice to build the string at most once per rustc, but we'd have to figure out where to put the necessary mutable state. |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (09a6b1d): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking 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 Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.9%, secondary 3.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 472.018s -> 473.009s (0.21%) |
… all? This demonstrates the theoretical limits of optimizing the quoting process.
df5de03
to
6765a77
Compare
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
(EXPERIMENT) Perf experiments for target-machine command-line quoting
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (3cad4c1): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking 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 Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.9%, secondary 2.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.0%, secondary -1.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 471.273s -> 471.264s (-0.00%) |
☔ The latest upstream changes (presumably #146879) made this pull request unmergeable. Please resolve the merge conflicts. |
This works because the only characters we care about escaping are ASCII characters, so forwarding non-ASCII UTF-8 bytes as-is still produces correct results.
r? ghost