Hi,

Quoting Samuel Thibault (2016-10-16 12:45:45)
> Johannes Schauer, on Sun 16 Oct 2016 12:40:39 +0200, wrote:
> > $ time schroot -c unstable-amd64-sbuild -n test --begin-session > /dev/null
> > schroot -c unstable-amd64-sbuild -n test --begin-session  0.00s user 0.01s 
> > system 13% cpu 0.086 total
> 
> Are you using filesystem snapshots?

I'm using directory chroots with overlayfs, which is the default created by
sbuild-createchroot.

> Really unpacking tarball schroot takes way more time on by amd64 box.

Just for fun, I created a tarball. Using lz4 compression I get:

$ time schroot -c unstable-amd64-sbuild -n test --begin-session > /dev/null
schroot -c unstable-amd64-sbuild -n test --begin-session > /dev/null  0.45s 
user 0.61s system 120% cpu 0.770 total

$ time schroot -c test --end-session
schroot -c test --end-session  0.01s user 0.06s system 33% cpu 0.212 total

So we are still talking about less than a second of schroot overhead per
package build (on my four year old Core i5 laptop which is probably much slower
than any buildd).

I'm asking all this because I wonder about the usefulness of the sudo mode and
how much sense it makes to continue maintaining it post Stretch.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to