I don't think it's worth slowing down builds in other cases, but that would imply the ability to tune it on the fly (or at least tweak settings without too much trouble). If somebody winds up building source packages for distro repos it might make sense in that one case to crank compression up to 9 to minimize repo space utilization and data transfer from their mirrors. I'm currently trying to get my build on buster working again which requires many iterations and that scenario is likely to come up again for many contributors. In my system I can spare 85MB of disk space to save 1m42s of build time (the delta of -0 and -6) as it's a tiny fraction of the space required to build and my time is more valuable than 85MB of disk. On some platforms xz threading is supported already. Multithreading alone saves about 7 minutes on my system. Tobu xz will be multithreaded by default so no pixz installation will be required in the future. I know the mechanism is being worked out above, but when that's in place I recommend using the "-0 -threads=0" tuning for normal builds. Using level 0 with all cores gives a 304MB file and takes just 16 seconds. There's a tiny size overhead with multithreaded writers in the xz format (lzma can't do this AFAIK). Using level 6 with all cores gives a 220MB file but takes 1 minute 59 seconds. based on How to use multi-threading for creating and extracting tar.xz. This gives a 218MB file and takes 9 minutes and 20 seconds on this hardware. I used the following command to compress a drive mounted to a folder. The current system uses xz level 6 compression and forces single threaded operation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |