Ömer Sinan Ağacan schrieb am 17.11.2019 um 09:22:
I think what we should do instead is that once it's clear that the
patch did not
introduce *accidental* increases in numbers (e.g. in !2100 I checked and
explained the increase in average residency, and showed that the increase makes
sense and
On November 17, 2019 3:22:59 AM EST, "Ömer Sinan Ağacan"
wrote:
>Hi,
>
>Currently we have a bunch of tests in testsuite/tests/perf/compiler for
>keeping
>compile time allocations, max residency etc. in the expected ranges and
>avoid
>introducing accidental compile time performance regressions.
Hi,
Currently we have a bunch of tests in testsuite/tests/perf/compiler for keeping
compile time allocations, max residency etc. in the expected ranges and avoid
introducing accidental compile time performance regressions.
This has a problem: we expect every MR to keep the compile time stats in
