Skip to content

10% performance regression after rollup #49051 #49168

Closed

Description

@michaelwoerister

http://perf.rust-lang.org/compare.html?start=39264539448e7ec5e98067859db71685393a4464&end=36b66873187e37a9d79adad89563088a9cb86028&stat=instructions:u

It's not quite clear what caused this regression, something in #49051. Pinging all committers from the range:
@jcowgill, @alexcrichton, @Eijebong, @mark-i-m, @kennytm, @Centril, @estebank, @snf, @ehuss, @Songbird0, @draganmladjenovic, @ExpHP, @petrochenkov

Any ideas? Did the rand crate get slower?

cc @rust-lang/wg-compiler-performance

Activity

  1. michaelwoerister commented on Mar 19, 2018

    @michaelwoerister
    MemberAuthor

    @alexcrichton oh, I see this regression is more or less expected due to ff227c4. Pity.

    This shouldn't affect stable and beta binaries, right?

  2. alexcrichton commented on Mar 19, 2018

    @alexcrichton
    Member

    Yeah this is almost for sure re-enabling multiple codegen units on dist builds. I do believe this affects stable/beta binaries, but such a change has already hit stable (aka today's stable release)

  3. michaelwoerister commented on Mar 19, 2018

    @michaelwoerister
    MemberAuthor

    Can we switch to one CGU for stable releases?

  4. alexcrichton commented on Mar 19, 2018

    @alexcrichton
    Member

    Unfortunately not really, we're seriously bleeding for time on CI as-is and we're looking for any wins we can get anywhere. We can leave this open if we ever get enough time on CI, but otherwise I think we just can't afford to do this today

  5. michaelwoerister commented on Mar 19, 2018

    @michaelwoerister
    MemberAuthor

    OK, thanks for the info. I'll close this issue since the regression is accounted for.

  6. sophiajt commented on Mar 19, 2018

    @sophiajt
    Contributor

    @michaelwoerister - sorry for jumping in, but is there a follow-up issue to track reclaiming this regressed time? One of our main deliverables this year is faster compile times, so each compile time regression is pretty serious.

    Apologies if I'm misunderstanding the thread, just making sure we're keeping track of where we slip and where we need to recover.

  7. michaelwoerister commented on Mar 19, 2018

    @michaelwoerister
    MemberAuthor

    @jonathandturner I have an item on my todo list for setting up a tracking issue about building our releases as optimized as possible (including PGO, once that's available, and maybe full LTO). Should be up later today.

  8. michaelwoerister commented on Mar 19, 2018

    @michaelwoerister
    MemberAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    I-compiletimeIssue: Problems and improvements with respect to compile times.WG-compiler-performanceWorking group: Compiler Performance

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions