linux-ext4 - Re: Porting Zfs features to ext2/3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 31 Jul 2008 03:50:17 +0300 (EEST)
From:	Szabolcs Szakacsits <szaka@...s-3g.org>
To:	Theodore Tso <tytso@....EDU>
cc:	linux-ext4@...r.kernel.org
Subject: Re: Porting Zfs features to ext2/3

On Tue, 29 Jul 2008, Theodore Tso wrote:
> On Tue, Jul 29, 2008 at 10:52:26PM +0000, Szabolcs Szakacsits wrote:
> > I did also an in memory test on a T9300@2.5, with disk I/O completely 
> > eliminated. Results:
> > 
> > tmpfs:    975 MB/sec
> > ntfs-3g:  889 MB/sec  (note, this FUSE driver is not optimized yet)
> > ext3:     675 MB/sec
> 
> Am I write in guessing that this test involved copying a single large
> file, with no seeks?  

Yes, it was writing a large file on a newly created, loop mounted image 
file.

> What happens if you try benchmarking unpacking a kernel source tar.bz2 
> file?  My guess is that ntfs-3g won't look as good.  :-)

It seems the tar.bz2 number is not so bad relatively but the metadata 
performance difference is much more visible by eliminating the compression 
overhead. The results are in second.

              ext3    ntfs-3g
  tar.bz2      7.7      12.4
  tar.gz       3.1       8.7
  tar          1.4       7.6

A few seconds could be improved but I think getting similar numbers will 
need major FUSE changes and non-trivial work to get rid of most contexts 
switches which indeed seem to be the bottleneck according to the profiling 
data.

	Szaka

--
NTFS-3G:  http://ntfs-3g.org

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html