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]
Message-ID: <47BAA064.5040509@vlnb.net>
Date:	Tue, 19 Feb 2008 12:24:52 +0300
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	Tomasz Chmielewski <mangoo@...g.org>
CC:	LKML <linux-fsdevel@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: very poor ext3 write performance on big filesystems?

Tomasz Chmielewski wrote:
> I have a 1.2 TB (of which 750 GB is used) filesystem which holds
> almost 200 millions of files.
> 1.2 TB doesn't make this filesystem that big, but 200 millions of files 
> is a decent number.
> 
> 
> Most of the files are hardlinked multiple times, some of them are
> hardlinked thousands of times.
> 
> 
> Recently I began removing some of unneeded files (or hardlinks) and to 
> my surprise, it takes longer than I initially expected.
> 
> 
> After cache is emptied (echo 3 > /proc/sys/vm/drop_caches) I can usually 
> remove about 50000-200000 files with moderate performance. I see up to 
> 5000 kB read/write from/to the disk, wa reported by top is usually 20-70%.
> 
> 
> After that, waiting for IO grows to 99%, and disk write speed is down to 
> 50 kB/s - 200 kB/s (fifty - two hundred kilobytes/s).
> 
> 
> Is it normal to expect the write speed go down to only few dozens of 
> kilobytes/s? Is it because of that many seeks? Can it be somehow 
> optimized? The machine has loads of free memory, perhaps it could be 
> uses better?
> 
> 
> Also, writing big files is very slow - it takes more than 4 minutes to 
> write and sync a 655 MB file (so, a little bit more than 1 MB/s) - 
> fragmentation perhaps?

It would be really interesting if you try your workload with XFS. In my 
experience, XFS considerably outperforms ext3 on big (> few hundreds MB) 
disks.

Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ