Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: new heap limits negatively affect performance #22692
What version of Go are you using (
Interesting. This is not expected behavior. However, my guess is that there's nothing special about these particular benchmarks. That commit certainly will change GC scheduling, and it may simply be that they typically didn't get a GC scheduled during them before and now do.
@TocarIP, could you try running each of these benchmarks in isolation and for a longer duration before and after that commit? That should help narrow down whether they're just being affected by scheduling artifacts from neighboring benchmarks.
(Thanks for keeping an eye on all the benchmarks!)