Re: [Genext2fs-devel] genext2fs takes too much execution time for large files
Brought to you by:
bestouff
From: bhaskar m. <ba...@gm...> - 2015-08-30 07:10:00
|
Hi Finn, Thanks for the reply , The error was consistent if the tarball of more than 2GB is present in the rootfs , else its pretty fast. to make 2GB rootfs image it takes 23 secs , but when this 2GB tarball rootfs is added , it takes significantly more time. yes i am using genext2fs-1.4.1 with all the yocto patches. 0001-Fix-warnings-remove-some-unused-macros.patch 0002-Add-put_blk-and-put_nod-routines.patch 0003-Add-get_blkmap-and-put_blkmap.patch 0004-Add-a-dirwalker-for-walking-through-directory-entrie.patch 0005-Make-filesystem-struct-not-an-overloay.patch 0006-Improve-the-efficiency-of-extend_blk.patch 0007-Move-hdlinks-into-the-filesystem-structure.patch 0008-Separate-out-the-creation-of-the-filesystem-structur.patch 0009-Move-byte-swapping-into-the-get-put-routines.patch 0010-Convert-over-to-keeping-the-filesystem-on-disk.patch 0011-Copy-files-into-the-filesystem-a-piece-at-a-time.patch 0012-Add-rev-1-support-large-file-support-and-rework-hole.patch 0013-Add-volume-id-support.patch 0014-Remove-unneeded-setting-of-s_reserved.patch 0015-Rework-creating-the-lost-found-directory.patch 0016-Fix-the-documentation-for-the-new-L-option.patch 0017-Fix-file-same-comparison.patch 0018-Handle-files-changing-while-we-are-working.patch 0019-Make-sure-superblock-is-clear-on-allocation.patch regards, Bhaskar On Sun, Aug 30, 2015 at 11:10 AM, Finn Thain <ft...@te...> wrote: > > On Sat, 29 Aug 2015, bhaskar malla wrote: > >> Hi All, I am having a typical scenario , where the genext2fs execution >> time is pretty high . I had my yocto build , once the build is finished >> , i am stuffing a 2.5 GB Tar ball in to the roots which made the rootfs >> size to 3.8 GB size >> $ genext2fs -i 1900 -z -b 3836864 -d export/dist mycustom.img >> On a machine which has : 32 cores 256Gb RAM , It takes 40 >> Mins ( after a fresh boot ) But when the same task is executed right >> after the yocto build on the same machine it takes 3 - 5 Hours Do let me >> know if that is a known thing. > > Performance would depend a lot on what files are cached. There are ways to > influence that if you want to try to get some repeatible timings. > >> Is there any way that i can bring down this time to less than 10 Mins. >> Any alternate tool to accomplish the same ? > > As you are using Yocto, are you also using their heavily patched > genext2fs-1.4.1? If you are, please try building the latest sources from > the upstream genext2fs CVS, and report bugs against that: > http://sourceforge.net/p/genext2fs/code/ > > BTW, the yocto project seems to have abandoned genext2fs: > https://bugzilla.yoctoproject.org/show_bug.cgi?id=6013 > So there's probably not a lot of point reporting bugs there. > > Their removal commit shows the patches they used to carry-- > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e2700768308c87db4bde04f6a1026d468489ddf4 > I checked a few at random and those patches or similar ones are present > upstream, so I wouldn't expect regressions. > > -- > >> Regards, Bhaskara Rao Malla >> |