In our previous blog post we saw why calling functions in Angular template expressions is bad practice and can have huge performance impact on your application.
Now it's time to take a look at Angular ChangeDetectionStrategy and see how it can help us improve the performances of our Angular applications.
At OctoPerf we created a load testing web application using Angular for the frontend.
The application features IDE capabilities (like IntelliJ Idea or VSCode) to create load testing scripts:
We faced several performance issues while creating such a complex web application. This blog post is the first of a series dedicated to common Angular performance issues and how to solve them.
This article is the last in a series of overviews of our new UI. You can find the others here:
This time we will dive into the changes we've made in the analysis.
The analysis page has remained mostly the same:
In this blog post we are going to look at some of the uncommon performance tests. By this we mean those scenarios that are not what we believe are commonly executed but those that are run periodically at best.
These uncommon scenarios should not necessarily take priority over the more common performance scenarios. They do add value by stressing parts of your application under test that may be missed by the more conventional tests.
We will discuss each scenario in turn and look at the benefits and some of the difficulties you may experience in designing these scenarios. We will also take time to give examples of when these scenarios would be useful.