How to Use New Relic for Performance Engineering and Load Testing
Performance engineering and load testing are critical parts of any modern software organization’s toolset. In fact, it’s increasingly common to see companies field dedicated load testing teams and environments—and many companies that don’t have such processes in place are quickly evolving in that direction. Driven by key performance indicators (KPIs), performance engineering and load testing for software applications have three main goals: More specifically, a typical load test might look like this: While there are plenty of tools available for generating the user load for a performance test, the New Relic platform (particularly New Relic APM, New Relic Infrastructure, and New Relic Browser) provides in-depth monitoring and features that can give crucial insights into the analysis of such tests—from browser response times to user sessions to application speed to utilization of backend resources.
Teams that instrument their load testing environments with New Relic get complete end-to-end visibility into the performance of their applications. This blog post presents a prescriptive 12-step overview (divided into 3 parts) of how to use New Relic for methodical load testing and root-cause analysis in your performance engineering process.