Paul D'Ambra

Are you able to join our [community slack](https://posthog com/slack)?

Adding comment from slack here -------- The difference in time spent is all in recorder.js. It looks like a conflict in a polyfill (although these performance graphs are really hard...

cc @rcmarron We've not tracked down the source of the performance impact from recordings here. But thought I'd tag you in case there are changes since 1.37.1 you think might...

Hey @rustho 👋 The incomparable @rcmarron discovered that in this case the site in question had a polyfill for older browsers. Recording relies on mutation observer and the polyfill version...

@abhisanson I'm going to close this issue since we've discovered the source. Please feel free to keep the conversation going in the community slack 💖

This was proving tricky to test locally... trying to reduce the size of the problem with #10910 first

This value is falling steadily (if slowly) by itself https://metrics.posthog.net/d/HFLsbSJnz/celery-insight-updates?orgId=1&var-manual_interval=10m&from=1658286347000&to=now&refresh=30s&viewPanel=24

Updated description @LuisChiej

@neilkakkar I think this covers the conversation here https://posthog.slack.com/archives/C0368RPHLQH/p1660727404221419 I'd be interested in releasing this so we can measure it *without trying to cache the count*

🤔 hmmm, #11168 _should_ only have affected display, not results. I'm being slow and not understanding though. Can we make an example insight?