Firefox 132 introduced a performance regression running in Docker

[soulgalore]

With the 132 release, I could spot a regression running in Docker on a couple of different bare metal servers. 132 introduced something that affected almost every metric, even TTFB. Switching between 131 and 132 there's an effect off 200-300 ms per metric. However when I tried running Firefox directly on the server, the regression is gone. Even more strange is that running in Docker with WebPageReplay, there's no regression.

I tried turning on the gecko profiler traces on the machine and when I turn them on, the regression goes away. When I checked the code, we wait 3 seconds after we turn on the log and when I remove that extra wait, I get the same behaviour with gecko profiler turned on.

I tried with 133 abet and the issue is still there.

I got a feeling that maybe some calling home functionality was added in 132 that disturbs the metrics, but when I turn on the HTTP log I run into #2202

The issue is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1930110

[soulgalore]

I wonder if https://support.mozilla.org/en-US/kb/third-party-cookies-firefox-tracking-protection is related?

[soulgalore]

Upstream issue updated: there are some new requests introduced in 132 for search suggestions.

[soulgalore]

The disabling of the search suggestion fixed it.