[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Time to merge scratch/correct-warning-pos into master, perhaps?

From: Eli Zaretskii
Subject: Re: Time to merge scratch/correct-warning-pos into master, perhaps?
Date: Sun, 23 Jan 2022 08:16:38 +0200

> Date: Sat, 22 Jan 2022 22:36:11 +0000
> From: Gregory Heytings <gregory@heytings.org>
> Cc: mattiase@acm.org, larsi@gnus.org, acm@muc.de, monnier@iro.umontreal.ca,
>  emacs-devel@gnu.org
> >>> That's consistent with what was reported at the beginning of this 
> >>> thread (~7% slowdown).  Byte compilation is expected to be slightly 
> >>> slower with this change.
> >>
> >> But make check does a lot more than byte compilation, or am I missing 
> >> something?
> >
> > Not much more, IME.
> >
> That's not what the numbers tell us (again 3b33a14380 vs 7922131bb2):
> make -j1 check: 181s (69s byte-compilation, 112s execution) vs 162s (58s 
> byte-compilation, 104s execution)
> make -j4 check: 45s (17s byte-compilation, 28s execution) vs 40s (15s 
> byte-compilation, 25s execution)
> make -j8 check: 26s (9s byte-compilation, 17s execution) vs 23s (7s 
> byte-compilation, 16s execution)
> In short, the compilation time in make check is slower (which is 
> expected), but the execution time in make check is also consistently ~7% 
> slower.

How did you separate compilation times from execution times, and what
does "execution time" stand for -- is that elapsed time, CPU time,
something else?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]