Announcement

Collapse
No announcement yet.

Tux3 File-System Claims To Be Faster Than Tmpfs

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • phoronix
    started a topic Tux3 File-System Claims To Be Faster Than Tmpfs

    Tux3 File-System Claims To Be Faster Than Tmpfs

    Phoronix: Tux3 File-System Claims To Be Faster Than Tmpfs

    The experimental Tux3 file-system has already made claims of being faster than EXT4. The latest claims out of the open-source file-system is that it's faster than Tmpfs, which is quite a feat given its very thin layer between VFS and SWAP...

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

  • energyman
    replied
    I own you nothing. Benchmarking with a broken fsync() and then claim to be faster is deceptive at best.

    It is like saying that a fused automatic fuse is much better because it can tolerate a much higher current.

    T'so and Chinner said it much better than I can.

    Leave a comment:


  • danielbot
    replied
    Originally posted by energyman View Post
    they uncovered NOTHING. They changed dbench and BROKE FSYNC.

    If that does not fill your mind with rage and your heart with fear I don't know what. fsync() must not return before the data is on the media. tux3 returns fsync() before the data is on the media.

    Basically: cheating. Read the emails yourself.
    Read the mails yourself, and notice the simple fact that all three filesystems ran exactly the same perfectly valid benchmark. I think you owe me an apology.

    Leave a comment:


  • energyman
    replied
    Originally posted by ssam View Post
    That's a good way to look at it. basically this has uncovered a bottle neck in tmpfs.

    tmpfs should always be fastest because there are lots of things that it does not need to worry about (eg unexpected shutdown safety). but there are probably bits in it that are slower then they could be, and nobody notices until they try to benchmark against a competing implementation.
    they uncovered NOTHING. They changed dbench and BROKE FSYNC.

    If that does not fill your mind with rage and your heart with fear I don't know what. fsync() must not return before the data is on the media. tux3 returns fsync() before the data is on the media.

    Basically: cheating. Read the emails yourself.

    Next time moronix posts some crap, check it for yourself. Especially with filesystems. Saying that moronix track record is spotty in that regard is an understatement.

    Leave a comment:


  • energyman
    replied
    and the first reply in the email-thread was D. Chinner debunking those claims.

    Phoronix REALLY should rename to moronix.

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by Teho View Post
    Gummiboot looks like a better choise to me. It uses EFISTUB and provides simple menu for choosing the kernel. It also support Boot loader Interface which is cool if you use systemd (systemd-analyze shows how much time the firmware and loader took to load and bootctl shows some other information). It also follows the Boot Loader Specification and is ridiculously easy to use; not to mention it automatically detects Windows and OS X installs.
    If you want to be fancy, and don't want to use GRUB2, then go for rEFInd. Compared to Gummiboot, it's more advanced and supports more eye-candy.

    Leave a comment:


  • Teho
    replied
    Originally posted by GreatEmerald View Post
    If you really want to get down to that, you should use EFISTUB with efibootmgr directly :P
    Gummiboot looks like a better choise to me. It uses EFISTUB and provides simple menu for choosing the kernel. It also support Boot loader Interface which is cool if you use systemd (systemd-analyze shows how much time the firmware and loader took to load and bootctl shows some other information). It also follows the Boot Loader Specification and is ridiculously easy to use; not to mention it automatically detects Windows and OS X installs.
    Last edited by Teho; 05-08-2013, 02:45 PM.

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by Teho View Post
    GRUB2 will become quite irrelevant in not so distant future as nearly all machines will ship with UEFI. Then it's better to put the /boot folder under EFI partition and use Gummiboot (or something similar) as loader. This way you can use any file system Linux kernel supports for everything else.
    If you really want to get down to that, you should use EFISTUB with efibootmgr directly :P

    Though honestly, if dual-booting, I still use GRUB2. The GRUB shell is always a good thing to have, and GRUB2 doesn't have any problems with being an UEFI program, either.

    Leave a comment:


  • Ericg
    replied
    Originally posted by Teho View Post
    GRUB2 will become quite irrelevant in not so distant future as nearly all machines will ship with UEFI. Then it's better to put the /boot folder under EFI partition and use Gummiboot (or something similar) as loader. This way you can use any file system Linux kernel supports for everything else.
    Trust me, I know, im looking forward to it. Been looking forward to it since the kernel first started getting the ability to be its own bootloader.

    Leave a comment:


  • Teho
    replied
    Originally posted by Ericg View Post
    that's not an Ubuntu issue, that's a grub issue, and grub2 should be able to boot from every FS the community uses now, including btrfs. tux3 will come once its mainlined
    GRUB2 will become quite irrelevant in not so distant future as nearly all machines will ship with UEFI. Then it's better to put the /boot folder under EFI partition and use Gummiboot (or something similar) as loader. This way you can use any file system Linux kernel supports for everything else.

    Leave a comment:

Working...
X