Skip to content

ocfs2: Inode Allocation Strategy Improvement.v2

Tao Ma ocfs2-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 3 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 3 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Ocfs2-devel] [PATCH 0/3] ocfs2: Inode Allocation Strategy Improvement.v2
Quoted 18 lines · tristan.ye
Quoted 17 lines · Tao Ma

Changelog from V1 to V2:
1. Modify some codes according to Mark's advice.
2. Attach some test statistics in the commit log of patch 3 and in this e-mail also. See below.

Hi all,
In ocfs2, when we create a fresh file system and create inodes in it,
they are contiguous and good for readdir+stat. While if we delete all the inodes and created again, the new inodes will get spread out and that isn't what we need. The core problem here is that the inode block search looks for the "emptiest" inode group to allocate from. So if an inode alloc file has many equally (or almost equally) empty groups, new inodes will tend to get spread out amongst them, which in turn can put them all over the disk. This is undesirable because directory operations on conceptually "nearby" inodes force a large number of seeks. For more details, please see
http://oss.oracle.com/osswiki/OCFS2/DesignDocs/InodeAllocationStrategy.

<snip>

Quoted 36 lines
Quoted 28 lines

echo 'y'|mkfs.ocfs2 -b 4K -C 4K -M local /dev/sda11

mount -t ocfs2 /dev/sda11 /mnt/ocfs2/
time tar jxvf /home/taoma/linux-2.6.28.tar.bz2 -C /mnt/ocfs2/ 1>/dev/null

real 0m20.548s 0m20.106s

umount /mnt/ocfs2/
echo 2 > /proc/sys/vm/drop_caches
mount -t ocfs2 /dev/sda11 /mnt/ocfs2/
time ls -lR /mnt/ocfs2/ 1>/dev/null

real 0m13.965s 0m13.766s

umount /mnt/ocfs2/
echo 2 > /proc/sys/vm/drop_caches
mount -t ocfs2 /dev/sda11 /mnt/ocfs2/
time rm /mnt/ocfs2/linux-2.6.28/ -rf

real 0m13.198s 0m13.091s

umount /mnt/ocfs2/
echo 2 > /proc/sys/vm/drop_caches
mount -t ocfs2 /dev/sda11 /mnt/ocfs2/
time tar jxvf /home/taoma/linux-2.6.28.tar.bz2 -C /mnt/ocfs2/ 1>/dev/null

real 0m23.022s 0m21.360s

Quoted 7 lines

umount /mnt/ocfs2/
echo 2 > /proc/sys/vm/drop_caches
mount -t ocfs2 /dev/sda11 /mnt/ocfs2/
time ls -lR /mnt/ocfs2/ 1>/dev/null

real 2m45.189s 0m15.019s
yes, that is it. ;) I don't know we can improve so much when I start up.

Quoted 6 lines

Tao,

I'm wondering why the 1st 'ls -lR' did not show us such a huge enhancement, are the system load(by uptime) simliar when doing your 2rd 'ls -lR' contrast tests? if so, that's a really significant gain!!!!:-),great congs!

Because when we do the 1st 'ls -lR', the inodes are almost contiguous. So the read is very fast. But with the 2nd 'ls -lR' because the old '2nd tar' spread inodes, so we have a poor performance. See
http://oss.oracle.com/osswiki/OCFS2/DesignDocs/InodeAllocationStrategy
for more details.

Quoted 5 lines

To get more persuasive testing results, i suggest you do the same tests by considerable times,and then a average statistic results should be more attractive to us:-), and it also minimize the influence of some exceptional system loads:-)

I don't have that many times to do a large number of tests. ;) Actually I only run my test cases about 2~3 times and give the average time. btw, I have left test env there, if you are interested, you can run it as you wish and give us a complete test result. :)

Regards,
Tao