Application performance is always fine, until it isn’t. Is a newly deployed feature too slow to use? Did the most recent release cause logins to take 10 times as long? Did the number of daily users increase so much that the infrastructure can no longer keep up? Are things just slow(er) for no apparent reason?
When performance inevitably becomes a problem, what are some useful tools and practices to
- Identify the immediate problem?
- Make sure it never becomes a problem again?
Fortunately, we already have various tools we can use to identify and fix performance issues: log files, profiler data, XREF reports, VSTs, and in an ideal world performance data from previous releases for comparison purposes.
During this session we will go over:
- How the aforementioned tools were used to make some impactful performance changes for a project.
- Some improvements, automations, and reports created on top of existing tools like the profiler, XREF reports, and VSTs.
- Some of the performance bottlenecks we found while making changes.
By the end of the session you should have a good idea of how to improve the performance of your own application, and some new tools to help you along the way
