Dear Thomas,
On Wed, Jan 2, 2019 at 7:51 PM Thomas Lange
wrote:
>
> > On Sun, 23 Dec 2018 22:52:36 +0900, Roger Shimizu
> > said:
>
> > On Sat, Aug 12, 2017 at 1:54 PM Thomas Lange
> > wrote:
> >>
> >> old version 1.0.89
> >> real1m26.940s
> >> user
On Sat, Aug 12, 2017 at 1:54 PM Thomas Lange
wrote:
>
> old version 1.0.89
> real1m26.940s
> user1m24.180s
> sys 0m2.420s
>
>
> including the patches
> real0m39.481s
> user0m50.444s
> sys 0m2.748s
have you compared with cdebootstrap?
-
I repeated my tests with debootstrap 1.0.106 on buster and everything
went OK. The directory that is generated using the original functions
file and the patched one are the same. Here are the debootstrap calls
I've tested so far:
debootstrap stretch
debootstrap --variant=minbase stretch
On Fri, 27 Jul 2018 11:25:40 +0200
Cyril Brulebois wrote:
> For some reason it seems I didn't follow up to this bug report but I'm
> pretty sure I did reply on debian-boot@ in some way: we need automated
> tests before and after those patches. And we need to make sure they
> yield the exact same
Hi,
Hideki Yamane (2018-07-27):
> As prepared MR in
> https://salsa.debian.org/installer-team/debootstrap/merge_requests/19
> I'll put it into 1.0.108, _after DebConf_ since I don't have GPG key on
> my laptop (I have the new one but it's not in keyring now).
>
> If some one want to push
Hi,
As prepared MR in
https://salsa.debian.org/installer-team/debootstrap/merge_requests/19
I'll put it into 1.0.108, _after DebConf_ since I don't have GPG key on
my laptop (I have the new one but it's not in keyring now).
If some one want to push 1.0.107 into repository, it's nice.
--
I forget something. During the run of debootstrap, I observed via
repeated ps -efl calls that often perl is running for a longer
time. Then I tried to use strace to see which exec(ve) calls takes a
long time. But I didn't managed to find out, instead I saw read calls
taking long. So I decided to
> On Thu, 7 Sep 2017 18:28:33 +0200, Tiago Ilieve
> said:
> Do you mind to share how you identified those slower parts of the
> code? Have you used a profiler or a similar tool?
I didn't used a profiler. I just look at the code and saw that the
Hi Thomas,
Do you mind to share how you identified those slower parts of the
code? Have you used a profiler or a similar tool?
I must say that I'm very impressed by your patches. :-)
Regards,
Tiago.
--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
Hi Thomas,
Thomas Lange (2017-08-12):
> Package: debootstrap
> Severity: normal
> Tags: patch
>
> I've wrote some patches, which speed up deboostrap a lot.
> Changes are only made to /usr/share/debootstrap/functions, mostly in
> the perl part, but also the number
Package: debootstrap
Severity: normal
Tags: patch
I've wrote some patches, which speed up deboostrap a lot.
Changes are only made to /usr/share/debootstrap/functions, mostly in
the perl part, but also the number of lines that are proceeded by
perl are reduced via egrep.
Here are some time
11 matches
Mail list logo