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

Disable BB GMP and MPFR, to fix performance regressions #32102

Merged
merged 1 commit into from
May 22, 2019

Conversation

staticfloat
Copy link
Member

Let's see if this compiles everywhere (fingers crossed for FreeBSD) and gives us the bigfloat performance back.

@fredrikekre
Copy link
Member

fredrikekre commented May 21, 2019

@nanosoldier runbenchmarks("linalg", vs=":master")

Edit: linalg 🤔

@nanosoldier
Copy link
Collaborator

RIP me.

@ararslan
Copy link
Member

@nanosoldier runbenchmarks("linalg", vs=":master")

@nanosoldier
Copy link
Collaborator

Long live Nanosoldier!

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @ararslan

@KristofferC
Copy link
Member

Why are you guys just testing LinAlg?

@nanosoldier runbenchmarks(ALL, vs=":master")

@vchuravy
Copy link
Member

Also we are not using BB for the release builds are we?

@KristofferC
Copy link
Member

I dunno, but it is important that what ends up in the binary is built the same way that what we test performance on.

@staticfloat
Copy link
Member Author

Also we are not using BB for the release builds are we?

We are using BB for the official releases. No reason not to, as far as we can tell.

@staticfloat
Copy link
Member Author

IMO we should rework nanosoldier to use the binaries built by the buildbots.

@ararslan
Copy link
Member

Why are you guys just testing LinAlg?

Hah yeah, I did it because it's what Fredrik did and I'm a 🐑. He apparently noticed that linalg wasn't the best choice given the edit.

@ararslan
Copy link
Member

I think the only dependency that Nanosoldier doesn't use BB for is LLVM.

@fredrikekre
Copy link
Member

fredrikekre commented May 21, 2019

Well, I copied you without looking carefully: #32097 (comment) :)

@ararslan
Copy link
Member

We're all 🐑
Untitled

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @ararslan

@ararslan
Copy link
Member

The relevant stuff looks good.

@KristofferC KristofferC merged commit b19fcbc into backports-release-1.2 May 22, 2019
@KristofferC
Copy link
Member

The memory regressions are weird... But they should not be related.

@KristofferC KristofferC deleted the sf/compile_gmp_mpfr branch May 22, 2019 06:56
@KristofferC
Copy link
Member

So should we just merge this into 1.3 + master as well since it seems like it is here to stay for a while?

@StefanKarpinski
Copy link
Member

Unless we can fix the issue somehow. @staticfloat, any thoughts?

@ViralBShah
Copy link
Member

ViralBShah commented Aug 19, 2019

How about we mark it for triage? So that if we hit a couple of RCs and not resolved, we can at least merge into 1.3 then.

@KristofferC
Copy link
Member

KristofferC commented Aug 19, 2019

I put #31759 on the 1.3 milestone at least.

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.

8 participants