Design with performance in mind

In the previous chapters we talked about High Availability architecture and installation instructions. In this part of the book we talk about developing your custom code with performance in mind. Both these activities can go in parallel, depending on your resource availability.

Performance of an application must be a focus area throughout the project cycle. Traditionally, performance testing has occurred late in the cycle, towards the end of the testing phase, or as part of the deployment process. This does not leave much time to identify and fix any performance issues, particularly if significant architecture changes are required. It is much more difficult and time consuming to improve performance in the later phases of the project cycle than to ensure that the application performs adequately from the beginning.

This section demonstrates the importance of performance testing early in a project, with focus on profiling.

This part of the book include:

xxxx