tristan.ye wrote: > On Sun, 2009-01-18 at 07:17 -0800, Sunil Mushran wrote: >> How big is this disk? Maybe one kernel tree untar is not be enough to >> expose the original issue. Also, use ls -i and/or debugfs to see if >> the inodes have some locality. > > Tao, sunil > > I've tested it out with more attempts, it may have something to do with > the disk size. but the root pause why i did not get a excited speed-up > performance gain was due to the iscsi-target(iscsi server) cache. the > operation in your testcase which was meant for cache dropping is aimed > at client side(a 'echo 2>/proc/sys/vm/drop_cache' only flush the fs's > cache for iscsi initor(isci client)). > > Tao, > > You can verify this by pausing the tests at the right point before we > start '2rd ls -lR', then flush the iscsi-target's cache by 'service > iscsi-target restart'(there may be a more graceful way to do this),after > this done, resume the tests, then you'll find the the realtime it > consumed will be up to 3 mins around:) cool, so I am very glad that you got the same result as mine. ;) > > Btw, i really saw lots of locality by 'ls -li' for inodes under a same > dir, take /mnt/ocfs2/linux-2.6.28/include/linux for instance, almost all > of its inodes are contiguous one by one regarding to its inode number. yeah, that is the desired behaviour with my 3 patches. :)
Then do you have any updated test statistics? Regards, Tao _______________________________________________ Ocfs2-devel mailing list [email protected] http://oss.oracle.com/mailman/listinfo/ocfs2-devel
