On Sun, Jul 17, 2022 at 12:21 AM Antonio Diaz Diaz <[email protected]> wrote: > > DustDFG wrote: > > I didn't try to know exact time of extraction but I got strange > > results when I tried to get exact time of listing the archive. > > Thanks. Your results show that tarlz lists the archive more than 2 times > faster than GNU tar, as expected. > > > The followinfg results for tarlz without -f option: > > > > $ time tarlz -t ./tde-i18n-20220504_e67bfc8629.tar.lz > > > > real 56m5.702s > > user 0m0.001s > > sys 0m0.006s > > > > I couldn't stand my patience so I interrupted process with CTRL+C > > Note the zeros in user and sys time. As you didn't specify an archive (with > -f), tarlz waits indefinitely trying to read it from standard input. You may > redirect the archive to standard input like this: > > $ time tarlz -t < tde-i18n-20220504_e67bfc8629.tar.lz > > Antonio. >
I tried extraction with tar and tarlz. tar time is 56s tarlz time is 27s I will think that bottleneck is really my disk because I can reproduce long extraction only when I am building dragora. It wasn't the first dragora build when I noticed this problem. When I will rebuild dragora, I will try to inspect this problem again but now I can't reproduce it. Thank you for your help
