Announcement

Collapse
No announcement yet.

LINUX FILESYSTEMS BENCHMARKS (includes REISER4 and EXT4).

Collapse
This topic is closed.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • LINUX FILESYSTEMS BENCHMARKS (includes REISER4 and EXT4).

    LINUX FILESYSTEMS BENCHMARKS
    (includes Reiser4 and Ext4)


    http://linuxhelp.150m.com/
    http://linux.50webs.org/

    RESULT: With compression, REISER4, absolutely SMASHED the other filesystems.

    No other filesystem came close (not even remotely close).

    Using REISER4 (gzip), rather than EXT2/3/4, saves you a truly amazing 816 - 213 = 603 MB (a 74% saving in disk space), and this, with little, or no, loss of performance when storing 655 MB of raw data. In fact, substantial performance increases were achieved in the bonnie++ benchmarks.

    We use the following filesystems:

    REISER4 gzip: Reiser4 using transparent gzip compression.
    REISER4 lzo: Reiser4 using transparent lzo compression.
    REISER4 Standard Reiser4 (with extents)
    EXT4 default Standard ext4.
    EXT4 extents ext4 with extents.
    NTFS3g Szabolcs Szakacsits' NTFS user-space driver.
    NTFS NTFS with Windows XP driver.

    Disk Usage in megabytes. Time in seconds. SMALLER is better.

    Code:
    .-------------------------------------------------.
    |File         |Disk |Copy |Copy |Tar  |Unzip| Del |
    |System       |Usage|655MB|655MB|Gzip |UnTar| 2.5 |
    |Type         | (MB)| (1) | (2) |655MB|655MB| Gig |
    .-------------------------------------------------.
    |REISER4 gzip | 213 | 148 |  68 |  83 |  48 |  70 |
    |REISER4 lzo  | 278 | 138 |  56 |  80 |  34 |  84 |
    |REISER4 tails| 673 | 148 |  63 |  78 |  33 |  65 |
    |REISER4      | 692 | 148 |  55 |  67 |  25 |  56 |
    |NTFS3g       | 772 |1333 |1426 | 585 | 767 | 194 |
    |NTFS         | 779 | 781 | 173 |   X |   X |   X |
    |REISER3      | 793 | 184 |  98 |  85 |  63 |  22 |
    |XFS          | 799 | 220 | 173 | 119 |  90 | 106 |
    |JFS          | 806 | 228 | 202 |  95 |  97 | 127 |
    |EXT4 extents | 806 | 162 |  55 |  69 |  36 |  32 |
    |EXT4 default | 816 | 174 |  70 |  74 |  42 |  50 |
    |EXT3         | 816 | 182 |  74 |  73 |  43 |  51 |
    |EXT2         | 816 | 201 |  82 |  73 |  39 |  67 |
    |FAT32        | 988 | 253 | 158 | 118 |  81 |  95 |
    .-------------------------------------------------.
    WHAT THE NUMBERS MEAN:

    The raw data (without filesystem meta-data, block alignment wastage, etc) was 655MB.
    It comprised 3 different copies of the Linux kernel sources.

    Disk Usage: The amount of disk used to store the data.
    Copy 655MB (1): Time taken to copy the data over a partition boundary.
    Copy 655MB (2): Time taken to copy the data within a partition.
    Tar Gzip 655MB: Time taken to Tar and Gzip the data.
    Unzip UnTar 655MB: Time taken to UnGzip and UnTar the data.
    Del 2.5 Gig: Time taken to Delete everything just written (about 2.5 Gig).

    Each test was preformed 5 times and the average value recorded.

    To get a feel for the performance increases that can be achieved by using compression, we look at the total time (in seconds) to run the test:

    bonnie++ -n128:128k:0 (bonnie++ is Version 1.93c)

    Code:
    .-------------------.
    | FILESYSTEM | TIME |
    .-------------------.
    |REISER4 lzo |  1938|
    |REISER4 gzip|  2295|
    |REISER4     |  3462|
    |EXT4        |  4408|
    |EXT2        |  4092|
    |JFS         |  4225|
    |EXT3        |  4421|
    |XFS         |  4625|
    |REISER3     |  6178|
    |FAT32       | 12342|
    |NTFS-3g     |>10414|
    .-------------------.
    The top two results use Reiser4 with compression. Since bonnie++ writes test files which are almost all zeros, compression speeds things up dramatically. That this is not the case in real world examples can be seen in the first test above where compression often does not speed things up. However, more importantly, it does not slow things down much, either.

    http://linuxhelp.150m.com/resources/fs-benchmarks.htm
    http://m.domaindlx.com/LinuxHelp/res...benchmarks.htm

    For more information regarding Reiser4, see these

    REISER4 HOWTOS.

    Some Amazing Filesystem Benchmarks. Which Filesystem is Best?
    http://linuxhelp.150m.com/resources/fs-benchmarks.htm

    Compiling yourself a 2.6.23 Kernel (with Reiser4 support). (2.6.24 Kernel Patch)
    http://linuxhelp.150m.com/installs/compile-kernel.htm

    Installing your favorite Linux Distro on Reiser4.
    http://linuxhelp.150m.com/installs/i...on-reiser4.htm

    Installing GRUB on a Reiser4 Partition.
    http://linuxhelp.150m.com/installs/grub-reiser4.htm
    Last edited by Jade; 06-19-2008, 08:22 PM.

  • Jade
    replied
    Michael: would you remove the S from FILESYSTEMS so that:

    LINUX FILESYSTEMS BENCHMARKS (includes REISER4 and EXT4).

    becomes

    LINUX FILESYSTEM BENCHMARKS (includes REISER4 and EXT4).

    Or perhaps add a colon:

    LINUX FILESYSTEMS: BENCHMARKS (includes REISER4 and EXT4).

    Thnx.

    Leave a comment:


  • lenrek
    replied
    Originally posted by some-guy View Post
    I was using Jade's definition of 'steal', that's why it's in ''
    Oh I know, I know...

    I just trying to say, we should try to correct their mistake, than continue to follow their mistake.

    Sometimes, they can never be corrected. It is, sadly, their flaw. We are not their guardian angel, neither should we be feeling responsible in correcting them. It is their own ignorant and stubbornness that lead them into such pitiful situation.

    However, by posting the most accurate information (as far as we know, and, as much as we can), hopefully, other readers who maybe reading this, will not be confused or fooled by them.

    Leave a comment:


  • some-guy
    replied
    Originally posted by lenrek View Post
    No no... We do not steal. We share, and build upon or base on the knowledge and experiences that have been accumulated, like any advances in human civilization.

    Those who use the term 'stealing' in OSS should be corrected, rather to continue using such misleading term.

    No, I am not a fan of RMS, but I do share some of his idea.
    I was using Jade's definition of 'steal', that's why it's in ''

    @Jade, It's a confusing issue, but IT IS A RUMOR, I was incorrect at saying a lie, however I'm sure the members on this forum are also against spreading rumors

    Leave a comment:


  • lenrek
    replied
    Originally posted by some-guy View Post
    'Stealing' ideas, isn't that what all distros do?
    If you don't want anything to be 'stolen' you make it proprietary.
    'Stealing' is what OSS is about, taking other people's work, and improving it
    No no... We do not steal. We share, and build upon or base on the knowledge and experiences that have been accumulated, like any advances in human civilization.

    Those who use the term 'stealing' in OSS should be corrected, rather to continue using such misleading term.

    No, I am not a fan of RMS, but I do share some of his idea.

    Leave a comment:


  • Jade
    replied
    Originally posted by some-guy View Post
    #2 (for the red), THIS IS A FAKE LIE YOU MADE UP, STOP SPREADING IT
    How do you know whether this is a correct or not?

    How could you possibly know?

    Why are you so certain that Reiser is not in prison because his file-system was better,... when you cannot possibly know whether this is true or not,... unless, of course, you do KNOW that Reiser has been framed (in order to kill Reiser4) and are trying to stop people even considering that this is the case.

    Reiser's trial was a huge joke.

    With a little reading up, any intelligent person can see this.

    No matter how the liars spin it,... it is quite apparent that the trial (& verdict) was a total joke.

    Who was funding this amazing travesty of justice.

    Where was the money coming from.

    My guess is from various software and database interests. From the same people (and their puppets in the media) who were already trying to kill Reiser4.

    Who paid judge Trina Thompson Stanley to have Reiser held in solitary confinement without bail on the basis of the amazingly flimsy blood and missing seat "evidence."

    So, who pushed for solitary confinement, without bail, on the basis of "evidence," that attorney Daniel Horowitz describes as, trace, weak and inaccurate.

    Oct 12, 2006: "There's not a lot of forensic evidence at all. Whatever they got is trace," Daniel Horowitz said.

    Oct 12, 2006: Investigators are "leaking sensational information that may not even be accurate," Daniel Horowitz complained.

    Oct 23, 2006: The prosecution's case is weak. "Here's the statement of probable cause, and I've read it, and their case is much weaker than they've said it is," Horowitz said.

    So, who pushed for solitary confinement, without bail, on the basis of "evidence," that two months later will be called, "utterly unconvincing," by the judge Julie Conger.

    Dec 11, 2006: judge Julie Conger comments that she found Oakland PD's theory utterly unconvincing on account of its placements and timings of people not matching what had been established in court.

    But, disregarding her own publicly stated conclusion, she allows the trial to proceed anyway. I guess judge Julie Conger was bought as well.

    On Sept. 29, 2006, just three weeks after the supposed murder, the FBI provides a "little bit of manpower," with the forensic investigation.

    How much pull and money, does it take to get the FBI involved in a missing person case so early in the case and before much of anything is actually known?

    Sept. 18, 2006: Guerrero said officers trailed Hans Reiser, both by car and by a special surveillance aircraft,...

    Who paid for around the clock surveillance by so many agents and for the special surveillance equipment?

    Who got the police so interested in this missing person case just two weeks after Nina Reiser had gone missing, that they devoted a fistful of dollars to it and with (at that time) no evidence, at all, of foul-play?

    Sept. 18, 2006. Alameda County commissioner Nancy Lonsdale declined to grant Reiser's custody request following testimony from Oakland police officers who said they had evidence that would argue against giving Reiser the children.

    Police said they couldn't share the evidence, not even with the commissioner.

    The police LIED when they claimed they couldn't share the evidence, not even with the commissioner, because they didn't have any evidence,... they just LIED.

    We now know that the police LIED. Who paid them to LIE.

    Who has enough pull to get the police to LIE?
    Last edited by Jade; 06-20-2008, 12:01 AM.

    Leave a comment:


  • Ex-Cyber
    replied
    Originally posted by StringCheesian View Post
    Jade, there seems to have been a misunderstanding.

    Those benchmarks are meaningful to you and Vighy for different reasons:
    You are interested in demonstrating Reiser4's superiority and supporting your allegation that it has been sabotaged. For that purpose, perhaps 2.6.20 is "more than adequate" in that it at least shows a decline.

    Vighy, on the other hand, is (like myself) simply curious to see how various filesystems compare in benchmarks, due to some enthusiasm or interest in Linux, filesystem performance, or all of the above. For that purpose, 2.6.20 and 2.6.13 are both ancient history.
    This is precisely the problem with this thread and these benchmarks; they exist for no other reason than to exercise Reiser4 fanboyism. It's really yet another in a vast array of "Reiser4 ought to be in mainline because it's fast and it Works For Me" arguments. The problem with this sort of argument is that it completely ignores the needs and concerns of the people who actually have to maintain mainline 5-10 years down the road.

    Leave a comment:


  • some-guy
    replied
    Originally posted by Jade View Post
    Are you brain dead or something,... which part of "the Reiser4 code has essentially not changed for years" didn't you understand.

    The Reiser4 code for 2.6.20 is (essentially) the same as for 2.6.26.

    Do a recursive diff.
    Everyone understood it, ext4 has changed so a proper benchmark would used 2.6.26
    Originally posted by Jade View Post
    If there are changes (like Reiser4 doesn't work any more) then they are most likely due to changes by kernel people coding outside of the Reiser4 code,... not due to changes in Reiser4 (coding outside Reiser4 could still include sabotage,... by changing the general environment in ways harmful to Reiser4's performance).


    Reiser is in prison because his file-system was better... End of story.
    #1, Reiser has to keep up with the kernel NOT the other way around

    #2 (for the red), THIS IS A FAKE LIE YOU MADE UP, STOP SPREADING IT
    It's like saying that 'at certain times, both shark attacks and ice cream sales go up' so does this mean ice cream is responsible for shark attacks?

    Leave a comment:


  • Jade
    replied
    Originally posted by StringCheesian View Post
    2.6.20 and 2.6.13 are both ancient history.
    Are you brain dead or something,... which part of "the Reiser4 code has essentially not changed for years" didn't you understand.

    The Reiser4 code for 2.6.20 is (essentially) the same as for 2.6.26.

    Do a recursive diff.

    If there are changes (like Reiser4 doesn't work any more) then they are most likely due to changes by kernel people coding outside of the Reiser4 code,... not due to changes in Reiser4 (coding outside Reiser4 could still include sabotage,... by changing the general environment in ways harmful to Reiser4's performance).

    Originally posted by Vighy View Post
    And don't tell me that Reiser is in prison because his file-system was better... I would not stop laughing for a month!
    Reiser is in prison because his file-system was better... End of story.
    Last edited by Jade; 06-19-2008, 08:38 PM.

    Leave a comment:


  • some-guy
    replied
    'Stealing' ideas, isn't that what all distros do?
    If you don't want anything to be 'stolen' you make it proprietary.
    'Stealing' is what OSS is about, taking other people's work, and improving it

    Leave a comment:

Working...
X