Investigating Performance Regressions with Trends Removed

We extended our performance monitoring solution to support PHP and Serverless, with plans to add Ruby and Java + Springboot support soon. A new view called Trends was introduced, allowing users to see the most improved and regressed transactions in relation to releases. This feature helped identify a potential performance regression caused by a bug in Snuba, our search infrastructure, which was exacerbated by new translators processing nested functions. To address this issue, a cache was built to store translated nodes, ensuring they were only processed once. The introduction of Trends demonstrates the value of performance monitoring and communicating with code.