Re: performance regressions in 15.0 [The Microsoft Dev Kit 2023 buildworld took about 6 minutes less time for jemalloc 5.3.0, not more, for non-debug contexts]

On Dec 9, 2025, at 07:22, Rozhuk Ivan <rozhuk.im@gmail.com> wrote:

> On Mon, 8 Dec 2025 09:23:52 -0800
> Mark Millard <marklmi@yahoo.com> wrote:
> 
>> But, as of yet, I've no good evidence for blaming
>> jemalloc as a major contributor to those timing
>> ratios --or for blaming any other specific part
>> of 15.0 .
> 
> If you want to bench jmalloc - there is another ways to do that without building something.
> Try to find some sythetic benchmarks.
> Also jmalloc can be build without OS rebuild and linked with bench.
> 
> This 2 things can reduce time to tests, but it will eliminate OS integation factors.
> Run same bench on different OS may give more info.
> 

[I've eliminated direct Email to most everyone
for this reply. There is not even minor new
technical content.]

At this point I'm more likely to explore if I
get similar ratios as ampere[13] do for some
port-package builds that have the large ratios on
ampere[13]. There are examples that are not as
overall time consuming for ampere[13] as what I've
already referenced (but are still non-trivial for
the time taken). As stands, I do not have a good
reproduce-the-issue context, much less one with
build time frames I'd be willing to deal with in
my environment.

===
Mark Millard
marklmi at yahoo.com