Results 1 to 10 of 14

Thread: A Patch That Can Make Btrfs 5~10% Faster

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,419

    Default A Patch That Can Make Btrfs 5~10% Faster

    Phoronix: A Patch That Can Make Btrfs 5~10% Faster

    A patch has been sent over to the Btrfs developers that can result in the next-generation Linux file-system being 5~10% faster in writes by introducing an extent buffer cache for each i-node...

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

  2. #2
    Join Date
    Dec 2008
    Posts
    150

    Default still no btrfsck

    I noticed the promised repair-capable btrfsck did not come out by Feb 14 as promised. Yet another deadline missed.

  3. #3
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,801

    Default

    Performance improvements are nice, but a patch that allows fsck would be more useful. Data safety > speed.

  4. #4
    Join Date
    Nov 2010
    Posts
    104

    Default

    Quote Originally Posted by jwilliams View Post
    I noticed the promised repair-capable btrfsck did not come out by Feb 14 as promised. Yet another deadline missed.
    btrfsck is going through QA internally at Oracle. It needs to be _safe_ before being released. Another thing is that Feb 14 was likely a deadline for Oracle (for proper QA) more so than a deadline for public release.

  5. #5
    Join Date
    Nov 2011
    Location
    Orange County, CA
    Posts
    78

    Default Disable COW

    Check out these patches to disable COW for specific data files (like DBs and VMs) that are better written in-place. I just built the patched chattr and I'm defragmenting and rebalancing my VM subvolumes right now.
    http://www.spinics.net/lists/linux-btrfs/msg09604.html
    http://www.spinics.net/lists/linux-btrfs/msg09605.html

  6. #6
    Join Date
    Dec 2008
    Posts
    150

    Default

    Quote Originally Posted by renkin View Post
    btrfsck is going through QA internally at Oracle. It needs to be _safe_ before being released. Another thing is that Feb 14 was likely a deadline for Oracle (for proper QA) more so than a deadline for public release.
    Strange for something that I thought would be open source. Release the source code and let everyone who wants to try it do the testing!

  7. #7
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,636

    Default

    Quote Originally Posted by jwilliams View Post
    Strange for something that I thought would be open source. Release the source code and let everyone who wants to try it do the testing!
    You don't want to release the source code of something that could (and without proper testing, most likely would) destroy the testers' drives... Better to make sure it's safe at least in local testing before that, and then release to public testing, and only after that declare it stable.

  8. #8
    Join Date
    Dec 2008
    Posts
    150

    Default

    Quote Originally Posted by GreatEmerald View Post
    You don't want to release the source code of something that could (and without proper testing, most likely would) destroy the testers' drives... Better to make sure it's safe at least in local testing before that, and then release to public testing, and only after that declare it stable.
    Then it will never be released, eternal vaporware.

    Good open source follows the release early, release often philosophy, even during alpha testing. More people looking at the code is better.

Posting Permissions

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