All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: Switch from tar.bz2 to tar.gz
Date: Mon, 5 Nov 2012 10:18:59 -0500	[thread overview]
Message-ID: <20121105151858.GA8311@edge> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C315A45@DFLE09.ent.ti.com>

Actually, neither gzip nor bzip2 use multiple threads, so it's running on a 
single core and won't benefit from 24 or even 124 cores...

Other than that, I don't mind switching to gzip for speed, slightly losing in 
size.

Denys


On Sun, Nov 04, 2012 at 02:06:01PM +0000, Cooper Jr., Franklin wrote:
> In our current setup tar.bz2 is the default file type used by image recipes. In classic arago we used tar.gz.
> 
> I was always curious why some of the image builds were taking a long time. I also noticed that installing the SDK using the installer also took a very long time.
> 
> I took arago-amsdk-image contents and created and extracted tar.gz and tar.bz2 files and timed the results.
> 
> extract tar.bz2
> real    2m20.402s
> user    2m15.800s
> sys     0m9.410s
> 
> extract tar.gz
> real    0m47.641s
> user    0m34.850s
> sys     0m10.860s
> 
> create tar.gz
> real    1m49.561s
> user    1m39.130s
> sys     0m4.420s
> 
> create tar.bz2
> real    6m10.851s
> user    6m8.490s
> sys     0m4.420s
> 
> It seems tar.bz2 provides better compression at the cost of extraction and compression speed. From a SDK perspective  some savings in size is not worth a significant increase in time to bitbake image recipes and neither is it worth the extra time to install a full blown SDK. I would also note that these test are done on a 24 core machine. I'm unsure how much these different compression algorithms utilize all the different cores but I am sure times on a traditional machine will be significantly longer. So is there any issue with me changing the default file type for images from tar.bz2 to tar.gz?
> 
> 
> Regards,
> Franklin Cooper Jr.
> Texas Instruments
> Application Engineer
> fcooper@ti.com<mailto:fcooper@ti.com>
> 

> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago



      parent reply	other threads:[~2012-11-05 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-04 14:06 Switch from tar.bz2 to tar.gz Cooper Jr., Franklin
2012-11-05 15:15 ` Maupin, Chase
2012-11-05 15:18 ` Denys Dmytriyenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121105151858.GA8311@edge \
    --to=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.