From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Voluspa <lista1@comhem.se>
Cc: akpm@osdl.org, arjan@infradead.org, Valdis.Kletnieks@vt.edu,
diegocg@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] readahead: initial method - expected read size - fix fastcall
Date: Thu, 8 Jun 2006 16:13:52 +0800 [thread overview]
Message-ID: <349754431.09938@ustc.edu.cn> (raw)
Message-ID: <20060608081352.GB5515@mail.ustc.edu.cn> (raw)
In-Reply-To: <20060608094356.5c1272cc.lista1@comhem.se>
It's interesting that copying of sparse file is more efficient with small
readahead size :) I get the same conclusion, though with smaller differences:
SUMMARY
user sys cpu total
ARA, 1M 0.15 6.28 82.80 7.73
ARA, 128k 0.14 6.09 85.60 7.26
STOCK, 128k 0.15 6.05 85.60 7.22
TEST CASE
wfg ~% ll work/sparse
-rw-r--r-- 1 wfg wfg 1.6G 2006-05-21 15:11 work/sparse
wfg ~% free
total used free shared buffers cached
Mem: 501 496 5 0 5 191
-/+ buffers/cache: 300 201
Swap: 127 0 127
wfg ~% time cp work/sparse /dev/null
ARA, 1M
cp work/sparse /dev/null 0.15s user 6.35s system 80% cpu 8.125 total
cp work/sparse /dev/null 0.14s user 6.28s system 84% cpu 7.556 total
cp work/sparse /dev/null 0.14s user 6.25s system 82% cpu 7.744 total
cp work/sparse /dev/null 0.15s user 6.23s system 85% cpu 7.495 total
cp work/sparse /dev/null 0.16s user 6.30s system 83% cpu 7.719 total
ARA, 128k
cp work/sparse /dev/null 0.15s user 6.07s system 86% cpu 7.224 total
cp work/sparse /dev/null 0.15s user 6.05s system 84% cpu 7.334 total
cp work/sparse /dev/null 0.14s user 6.18s system 86% cpu 7.328 total
cp work/sparse /dev/null 0.13s user 6.11s system 86% cpu 7.217 total
cp work/sparse /dev/null 0.14s user 6.06s system 86% cpu 7.179 total
STOCK, 128k
cp work/sparse /dev/null 0.16s user 6.01s system 86% cpu 7.162 total
cp work/sparse /dev/null 0.14s user 6.10s system 86% cpu 7.222 total
cp work/sparse /dev/null 0.14s user 6.04s system 86% cpu 7.186 total
cp work/sparse /dev/null 0.15s user 6.02s system 85% cpu 7.210 total
cp work/sparse /dev/null 0.14s user 6.09s system 85% cpu 7.320 total
Wu
next prev parent reply other threads:[~2006-06-08 8:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 7:34 [PATCH] readahead: initial method - expected read size - fix fastcall Fengguang Wu
2006-06-04 7:34 ` Fengguang Wu
2006-06-04 9:07 ` Andrew Morton
2006-06-04 9:25 ` Arjan van de Ven
2006-06-05 1:17 ` Voluspa
2006-06-05 8:00 ` Arjan van de Ven
2006-06-06 2:26 ` Fengguang Wu
2006-06-06 2:26 ` Fengguang Wu
2006-06-08 7:31 ` Voluspa
2006-06-08 7:57 ` Fengguang Wu
2006-06-08 7:57 ` Fengguang Wu
2006-06-06 2:57 ` Fengguang Wu
2006-06-06 2:57 ` Fengguang Wu
2006-06-08 7:43 ` Voluspa
2006-06-08 8:13 ` Fengguang Wu [this message]
2006-06-08 8:13 ` Fengguang Wu
2006-06-08 8:28 ` Voluspa
2006-06-08 8:50 ` Fengguang Wu
2006-06-08 8:50 ` Fengguang Wu
2006-06-08 10:04 ` Voluspa
2006-06-04 12:13 ` [PATCH] readahead: call scheme - fix fastcall readahead_cache_hit() Fengguang Wu
2006-06-04 12:13 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 3:36 Adaptive Readahead V14 - statistics question Voluspa
2006-05-30 6:40 ` Wu Fengguang
2006-05-30 6:40 ` Wu Fengguang
2006-05-30 16:49 ` Valdis.Kletnieks
2006-05-31 21:06 ` Diego Calleja
2006-05-31 21:50 ` Voluspa
2006-06-01 5:51 ` Fengguang Wu
2006-06-01 5:51 ` Fengguang Wu
2006-06-01 6:35 ` Voluspa
2006-06-08 8:04 ` Voluspa
2006-06-08 11:37 ` adaptive readahead overheads Fengguang Wu
2006-06-08 11:37 ` Fengguang Wu
2006-06-08 12:25 ` Voluspa
2006-06-08 12:39 ` Fengguang Wu
2006-06-08 12:39 ` Fengguang Wu
2006-06-08 13:05 ` Andi Kleen
2006-06-08 14:00 ` Jens Axboe
[not found] ` <448493E9.9030203@samwel.tk>
2006-06-06 3:34 ` Adaptive Readahead V14 - statistics question Wu Fengguang
2006-06-06 3:34 ` Wu Fengguang
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=349754431.09938@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@comhem.se \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.