As performance engineers, we understand the importance of software testing during and after development in order to identify any and all performance bottlenecks. Due to various constraints—whether a scaled-down test environment, data volume, or code integration limitations—it’s not always possible to catch all bugs in test. If performance bottlenecks are not identified and resolved in a timely manner, there’s a chance customers may be impacted. As a result, anomaly detection in production takes on an even bigger significance.
The scale at which this kind of anomaly detection needs to be done is noteworthy—few servers in test versus thousands of servers in production, with time being of the utmost essence. That’s why anomaly detection at scale is one the biggest challenges for a performance engineer. One of the most widely used techniques to identify performance bugs is to look at time series data for the various metrics, which can then be used to find potential problems. However, this approach doesn’t scale well in production, even if time series data can be consolidated into a few charts. Tuli Nivas shares techniques that address how time consuming this kind of analysis can be and demonstrates how applying simple statistics and basic linear regression principles can improve productivity of a performance engineer tenfold or more.
This session is sponsored by Salesforce.
Tuli Nivas is a principal performance engineer at Salesforce with extensive experience in design and implementation of test automation and monitoring frameworks. Her interests lie in software testing, cloud computing, big data analytics, systems engineering, and architecture. Tuli holds a PhD in computer science with a focus on building processes to set up robust and fault-tolerant performance engineering systems.
Comments on this page are now closed.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org