Skip to content

Add diesel to the benchmark suite #8030

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

Merged
merged 1 commit into from
Mar 15, 2021

Conversation

weiznich
Copy link
Contributor

This commit adds diesel to the continuosly run benchmark suite. Diesel
heavily relies internally on macro generated code. Additionally there
are lots of complicated trait releations used as part of their API.
Therefore this benchmark will be quite sensitive to:

  • Performance related changes in the macro expanding code
  • Performance related changes while resolving trait bounds

CC #7950

cc @lnicola

This commit adds diesel to the continuosly run benchmark suite. Diesel
heavily relies internally on macro generated code. Additionally there
are lots of complicated trait releations used as part of their API.
Therefore this benchmark will be quite sensitive to:
* Performance related changes in the macro expanding code
* Performance related changes while resolving trait bounds

CC rust-lang#7950
@lnicola
Copy link
Member

lnicola commented Mar 15, 2021

changelog internal add diesel to the benchmark suite.

@lnicola
Copy link
Member

lnicola commented Mar 15, 2021

Looks like this should take about 5-6 minutes on CI. It might be pretty painful, but let's tentatively merge it.

I checked ripgrep and webrender and they don't seem to have changed in the meanwhile.

bors r+

@bors
Copy link
Contributor

bors bot commented Mar 15, 2021

@bors bors bot merged commit 633637b into rust-lang:master Mar 15, 2021
@@ -26,7 +26,7 @@ impl flags::Metrics {
}
{
let _d = pushd("./target/rustc-perf")?;
cmd!("git reset --hard 1d9288b0da7febf2599917da1b57dc241a1af033").run()?;
cmd!("git reset --hard c52ee623e231e7690a93be88d943016968c1036b").run()?;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add this hash to JSON we publish to the metrics repo, so that it's easy to see when we update the test suite.

@lnicola
Copy link
Member

lnicola commented Mar 15, 2021

Great, this broke the metrics dashboard :-).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants