The fact is that if autotests are still being written to maintain quality in some web projects, then few people are involved in performance control at the development stage in principle. A web project with both autotests and code benchmarks is a rarity. Developers are much more likely and for reasonable reasons to use the following heuristics with a good value-for-money ratio:
- Queries to MySQL (further we will cite this popular database as an example) go through a fairly adequate API that uses indexes (although we do not see exactly how indexes are used by the scheduler and what their cardinality is).
- The results of executing queries to the database and heavy pieces of code are cached.
- The developer checked the construction of the web page 3.14 times in the browser, and if it doesn’t slow down at first glance, then everything is OK.
Let’s take caching. The developer often …
View More Why Do You Need Load Testing For A Website?