LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LKML <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: very poor ext3 write performance on big filesystems?
Date: Mon, 18 Feb 2008 13:57:16 +0100 [thread overview]
Message-ID: <47B980AC.2080806@wpkg.org> (raw)
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?
+ dd if=/dev/zero of=testfile bs=64k count=10000
10000+0 records in
10000+0 records out
655360000 bytes (655 MB) copied, 3,12109 seconds, 210 MB/s
+ sync
0.00user 2.14system 4:06.76elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+883minor)pagefaults 0swaps
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda 1,2T 697G 452G 61% /mnt/iscsi_backup
# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda 154M 20M 134M 13% /mnt/iscsi_backup
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2008-02-18 12:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 12:57 Tomasz Chmielewski [this message]
2008-02-18 14:03 ` Andi Kleen
2008-02-18 14:16 ` Theodore Tso
2008-02-18 15:02 ` Tomasz Chmielewski
2008-02-18 15:16 ` Theodore Tso
2008-02-18 15:57 ` Andi Kleen
2008-02-18 15:35 ` Theodore Tso
2008-02-20 10:57 ` Jan Engelhardt
2008-02-20 17:44 ` David Rees
2008-02-20 18:08 ` Jan Engelhardt
2008-02-18 16:16 ` Tomasz Chmielewski
2008-02-18 18:45 ` Theodore Tso
2008-02-18 15:18 ` Andi Kleen
2008-02-18 15:03 ` Theodore Tso
2008-02-19 14:54 ` Tomasz Chmielewski
2008-02-19 15:06 ` Chris Mason
2008-02-19 15:21 ` Tomasz Chmielewski
2008-02-19 16:04 ` Chris Mason
2008-02-19 18:29 ` Mark Lord
2008-02-19 18:41 ` Mark Lord
2008-02-19 18:58 ` Paulo Marques
2008-02-19 22:33 ` Mark Lord
2008-02-27 11:20 ` Tomasz Chmielewski
2008-02-27 20:03 ` Andreas Dilger
2008-02-27 20:25 ` Tomasz Chmielewski
2008-03-01 20:04 ` Bill Davidsen
2008-02-19 9:24 ` Vladislav Bolkhovitin
[not found] <9YdLC-75W-51@gated-at.bofh.it>
[not found] ` <9YeRh-Gq-39@gated-at.bofh.it>
[not found] ` <9Yf0W-SX-19@gated-at.bofh.it>
[not found] ` <9YfNi-2da-23@gated-at.bofh.it>
[not found] ` <9YfWL-2pZ-1@gated-at.bofh.it>
[not found] ` <9Yg6H-2DJ-23@gated-at.bofh.it>
2008-02-19 13:14 ` Paul Slootman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B980AC.2080806@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: very poor ext3 write performance on big filesystems?' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).