Identifying Client-Side Performance Bottlenecks

What you'll learn

• One is a developer may want to just check their latest build against performance numbers and they can do that. The typical use case is CI integration where every time there is a pull request and a new build gets generated, it gets profiled and we can detect regressions in performance.
• Also, some of our customers use it as a release criteria. So they set up an actual budget of what performance numbers are acceptable for certain typical UI interactions, and then they can check against those numbers.
• And then finally, in production when you’re talking about a customer reported issue, you can actually rerun it through Nimble and get some results to look at.

Topics covered