Add PID to LLVM PGO profile path

[Kobzol]

This is a continuation of #97110, which adds PID to the filename pattern of LLVM profiles. It also adds some metrics to the pgo.sh script, so that we can observe how many profiles there are and how large are they.

r? @lqd

[Kobzol]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit ce5e532281e3313a848839a10ad80eb14ff74140 with merge 561e1f5d82bcf2d1e3175b9ece6115f0ded948f0...

[bors]

💥 Test timed out

[Kobzol]

@rust-timer build 561e1f5

[Kobzol]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit ce5e532281e3313a848839a10ad80eb14ff74140 with merge 7b52047cca30b8de507625c49eed570f987fd739...

[bors]

☀️ Try build successful - checks-actions
Build commit: 7b52047cca30b8de507625c49eed570f987fd739 (7b52047cca30b8de507625c49eed570f987fd739)

[rust-timer]

Queued 7b52047cca30b8de507625c49eed570f987fd739 with parent e5732a2, future comparison URL.

[rust-timer]

Finished benchmarking commit (7b52047cca30b8de507625c49eed570f987fd739): comparison url.

Summary:

• Primary benchmarks: 😿 relevant regressions found
• Secondary benchmarks: 😿 relevant regressions found

	Regressions 😿 (primary)	Regressions 😿 (secondary)	Improvements 🎉 (primary)	Improvements 🎉 (secondary)	All 😿 🎉 (primary)
count1	98	50	0	0	98
mean2	2.2%	2.1%	N/A	N/A	2.2%
max	4.6%	4.3%	N/A	N/A	4.6%

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

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

Footnotes

1. number of relevant changes ↩

2. the arithmetic mean of the percent change ↩

[Kobzol]

It seems that source-level instrumentation for LLVM is not better than IR level instrumentation. Let's try once more with IR level instrumentation done by clang.

[Kobzol]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 1a6f29b0b3e8125c5b010903f7c7e078b720f829 with merge 5bc8c8bd82038990ccbf68b7bab76cd547a2c339...

[bors]

☀️ Try build successful - checks-actions
Build commit: 5bc8c8bd82038990ccbf68b7bab76cd547a2c339 (5bc8c8bd82038990ccbf68b7bab76cd547a2c339)

[rust-timer]

Queued 5bc8c8bd82038990ccbf68b7bab76cd547a2c339 with parent 10d9ecd, future comparison URL.

[rust-timer]

Finished benchmarking commit (5bc8c8bd82038990ccbf68b7bab76cd547a2c339): comparison url.

Summary:

• Primary benchmarks: 🎉 relevant improvements found
• Secondary benchmarks: 🎉 relevant improvements found

	Regressions 😿 (primary)	Regressions 😿 (secondary)	Improvements 🎉 (primary)	Improvements 🎉 (secondary)	All 😿 🎉 (primary)
count1	0	0	28	12	28
mean2	N/A	N/A	-0.7%	-0.8%	-0.7%
max	N/A	N/A	-1.0%	-0.9%	-1.0%

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf.

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

Footnotes

1. number of relevant changes ↩

2. the arithmetic mean of the percent change ↩

[Mark-Simulacrum]

@bors r+ rollup=never

[bors]

📌 Commit 0b09222d20729f3d28f10e777952f107b65d26dc has been approved by Mark-Simulacrum

[bors]

⌛ Testing commit 0b09222d20729f3d28f10e777952f107b65d26dc with merge 0433bd1f871f18705cfb2d0677eff68bf318abf9...

[bors]

💔 Test failed - checks-actions

[Kobzol]

@bors retry

[Kobzol]

@Mark-Simulacrum Can you reapprove this please? Before one benchmark was wrong after a rebase, I have fixed it.

[Mark-Simulacrum]

@bors r+

[bors]

📌 Commit 87e97c9 has been approved by Mark-Simulacrum

[bors]

⌛ Testing commit 87e97c9 with merge 6364179...

[bors]

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 6364179 to master...

[rust-timer]

Finished benchmarking commit (6364179): comparison url.

Instruction count

• Primary benchmarks: 🎉 relevant improvements found
• Secondary benchmarks: 🎉 relevant improvements found

	mean1	max	count2
Regressions 😿 (primary)	N/A	N/A	0
Regressions 😿 (secondary)	N/A	N/A	0
Improvements 🎉 (primary)	-0.6%	-0.8%	20
Improvements 🎉 (secondary)	-0.7%	-1.0%	8
All 😿🎉 (primary)	-0.6%	-0.8%	20

Max RSS (memory usage)

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

Cycles

Results

• Primary benchmarks: 🎉 relevant improvement found
• Secondary benchmarks: no relevant changes found

	mean1	max	count2
Regressions 😿 (primary)	N/A	N/A	0
Regressions 😿 (secondary)	N/A	N/A	0
Improvements 🎉 (primary)	-3.5%	-3.5%	1
Improvements 🎉 (secondary)	N/A	N/A	0
All 😿🎉 (primary)	-3.5%	-3.5%	1

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression

Footnotes

1. the arithmetic mean of the percent change ↩ ↩²

2. number of relevant changes ↩ ↩²