JFFS2, UBIFS, and the growth of flash storage
JFFS2, UBIFS, and the growth of flash storage
Posted Dec 12, 2012 1:18 UTC (Wed) by neilbrown (subscriber, #359)In reply to: JFFS2, UBIFS, and the growth of flash storage by arnd
Parent article: JFFS2, UBIFS, and the growth of flash storage
Thanks for the suggestion. I hadn't used the active_logs mount option. I just ran my script with that option added and it didn't make much difference.
The numbers I get for the original and the active_logs=4 runs are:
f2fs-default-2: write kernel 113.738 121.853 118.412 read kernel 150.369 270.465 175.724 du -s kernel 48.393 48.908 48.6091 rm -r kernel 0.333 0.384 0.36 write files 837.503 read files 571.196 f2fs-active_logs: write kernel 111.966 120.791 116.571 read kernel 148.364 238.796 163.316 du -s kernel 48.111 49.623 49.1534 rm -r kernel 0.335 0.365 0.3489 write files 1190.29 read files 563.56Where there are 3 numbers they are min/max/mean of 10 runs.
Reading small files seems faster, but the numbers were already noisy - about half the individual results were within 5 seconds of the minimum. which is much the same in both cases.
The write-large-files test is quite a bit slower. I probably need to do a couple more runs before I know what that means.
So it looks like I wasn't hitting the possible too-many-erase-blocks-open case in this test.
Posted Dec 12, 2012 21:14 UTC (Wed)
by arnd (subscriber, #8866)
[Link]
I agree on the read numbers, they are probably just in the noise because in theory there is no difference at all based on the mount option.
One thing that would make a very significant difference though is whether the file system is aged and how full it is, but that is true for all of the tests you did.
JFFS2, UBIFS, and the growth of flash storage