Results 1 to 10 of 13

Thread: Gosh, Our Test Farm Already Finds Big Regression

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,770

    Default Gosh, Our Test Farm Already Finds Big Regression

    Phoronix: Gosh, Our Test Farm Already Finds Big Regression

    Back in October we made it possible to autonomously find performance regressions in a project's code-base by leveraging the Phoronix Test Suite atop Git's bisect command. A new Phoronix Test Suite module was created that would automatically run a binary search on a defined code-base and keep running the specified test(s) on each revision and then traverse to the next using Git bisect until the lone commit causing the defined regression was located...

    http://www.phoronix.com/vr.php?view=Nzc5NA

  2. #2
    Join Date
    Jul 2009
    Posts
    12

    Default

    I'm curious if you could compare older versions with current kernels sometimes in the future. Just to see if 2.6.32 is really faster than 2.6.12/22/etc. (if possible - btrfs-performance in 2.6.12 wouldn't be very useful ;-) )

  3. #3
    Join Date
    Dec 2007
    Location
    Edinburgh, Scotland
    Posts
    576

    Default

    Seriously why cant you folk just raise a bug!!

  4. #4
    Join Date
    Jul 2008
    Posts
    69

    Default

    And you are holding off disclosing this because???? Seriously, what do you have to gain by not submitting this. Every day you wait brings the release date for .33 closer, and makes it less likely that there will be time to create/test patches.

    I don't even know what to call this move. It's not selfish because there's not really anything to gain/

  5. #5
    Join Date
    Jun 2006
    Location
    Portugal
    Posts
    527

    Default

    Quote Originally Posted by jbrown96 View Post
    And you are holding off disclosing this because???? Seriously, what do you have to gain by not submitting this. Every day you wait brings the release date for .33 closer, and makes it less likely that there will be time to create/test patches.

    I don't even know what to call this move. It's not selfish because there's not really anything to gain/
    .33 should still be 3 months away or something -- the merge window is still open and -rc1 hasn't even come out yet.
    And if it's a regression, then a patch fixing it would still be accepted outside the merge window, and basically anytime until the final release.

  6. #6
    Join Date
    Sep 2006
    Location
    PL
    Posts
    910

    Default

    And if it's a regression, then a patch fixing it would still be accepted outside the merge window, and basically anytime until the final release.
    waiting and not disclosing security bugs is bad.

    performance regressions are not as critical, but i think not disclosing them during merge window is a fatal mistake, because it might be very difficult to revert the problematic merge.

    I don't even know what to call this move. It's not selfish because there's not really anything to gain/
    publicity stunt.
    Last edited by yoshi314; 12-11-2009 at 05:06 AM.

  7. #7

    Default

    This delay is just not so the public interface can be finished up but to also ensure the issue can be reproduced on other platforms and that the commit that's isolated is indeed correct. This will hopefully be all completed by Monday so it's really not much of a delay.

  8. #8
    Join Date
    Feb 2009
    Posts
    116

    Default Cool.

    Cool.

    For the bashers: It's their software, it's their money, it's their time. They release when and the way they like it.

  9. #9

    Default

    Quote Originally Posted by talvik View Post
    Cool.

    For the bashers: It's their software, it's their money, it's their time. They release when and the way they like it.
    Yeah, what a usefull information...

    Those who comment (bash in your opinion) probably want to have this regression fixed and probably wondered if Phoronix will help with this. And it seems they will. Thanks.

  10. #10

    Default

    Ugh, there's more regressions... Well, all of the data will be publicly out next week -- and from there on out in a real-time stream -- so more can join in on the testing and bisecting fun if you wish.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •