[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Time to merge scratch/correct-warning-pos into master, perhaps?
From: |
Alan Mackenzie |
Subject: |
Re: Time to merge scratch/correct-warning-pos into master, perhaps? |
Date: |
Sat, 22 Jan 2022 18:35:15 +0000 |
Hello, Gregory.
On Sat, Jan 22, 2022 at 17:02:43 +0000, Gregory Heytings wrote:
> >> I'd like to see the results from elisp-benchmarks with and without this
> >> patch set, please.
> > In my experience, the elisp-benchmarks are very much not representative
> > of actual elisp usage, and I have done quite some benchmarking for other
> > reasons lately.
> I don't know what benchmarks would be representative of actual elisp
> usage, but on my build machine both make bootstrap and make check are
> consistently ~8% slower on correct-warning-pos vs master:
> make -j1 bootstrap: 649s vs 596s
> make -j4 bootstrap: 257s vs 238s
> make -j8 bootstrap: 198s vs 183s
> make -j1 check: 178s vs 162s
> make -j4 check: 44s vs 40s
> make -j8 check: 26s vs 24s
This is true, and expected. However the bootstrap is still faster than
it was this time last week, due to commit
10083e788f7349fa363d100687dc3d94bea88f57 on Thursday.
--
Alan Mackenzie (Nuremberg, Germany).
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, (continued)
- Message not available
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/25
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/25
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/26
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/26
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Stefan Monnier, 2022/01/26
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/26
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Alan Mackenzie, 2022/01/26
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?,
Alan Mackenzie <=
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/23
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/23
Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Stefan Monnier, 2022/01/15
Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Brahimi Saifullah, 2022/01/15