Maintaining Web applications at optimal performance levels is a necessary requirement for ensuring customer satisfaction and organizational efficiency. Platform’s Performance module provides tools for optimizing Web application performance by employing a detailed performance enhancement method - "The Performance Lifecycle". The Performance Lifecycle is a process of calibrating Platform to provide optimal performance boost to business critical Web applications.
Deploying Platform in organizations will improve the overall performance of Web applications by:
Enhancing code and download performance.
Employing full and partial page caching capabilities.
Preserving memory consumption through file compression.
The use of Platform Performance tools in development and production environments provides a means for testing and maintaining Web application performance.
The following illustration displays the three stages of the Performance Lifecycle.
The Platform Performance Lifecycle is an iterative cycle for analyzing Web application performance. The purpose of this cycle is to identify areas that require Platform calibration and areas that require PHP code optimization.
The Performance Lifecycle Baselines (stages) are as follows:
The first Baseline is the Zend Baseline. This baseline measures performance based on Platform’s default parameters that are immediately activated upon installation. The default parameters are, Event Trigger settings, Code Optimization and Code Acceleration. Once Platform is installed, these components automatically begin to work on the PHP code. The result is an immediate improvement to the Web application and initial PHP Intelligence event generation (based on default Event Trigger settings).
The purpose of the Zend Baseline is to evaluate overall performance in relation to the Platform defaults. This information is used as an initial starting point for subsequent calibration and optimizations.
In the Zend Baseline stage, it is common to experience abnormal event generation behavior (too many or too little events generated). This is a normal part of the initial calibration stage, necessary for identifying how to adjust performance settings to obtain optimal Web application performance.
The second Baseline is the actual calibration process. Based on information collected and observed in the first Baseline, the performance settings can be calibrated to suit each organization’s specific Web application. The Site Baseline enables one to obtain insight into the overall performance of the Web application. Once the Site Baseline is established by configuring Event Triggers these events can be further analyzed to evaluate the mode of action required to optimize the Web application’s performance. At this point it is recommended to perform a Site Analysis to benchmark the Web application. The Benchmark information provides an initial indication of the Web application’s current performance before applying the additional performance tools. This will provide a point of comparison to view improvements that occur after subsequent optimization is done with Platform.
After the Site analysis, the PHP code can be optimized. Optimization is obtained by implementing performance tools to areas in the PHP that exceed the Site Baseline settings (still generate events).
There are four possible choices for adding performance features to PHP code:
Full page caching
Partial page caching
Blacklist files or directories
Completing optimization of the Site Baseline brings us to the Optimized Baseline.
The Optimized Baseline represents the stage where the Web application is optimized and Platform is calibrated with the Web application. From this stable stage all that is left to do is to let Platform perform regular production monitoring.
When the Web application is re-deployed or changes are made, this process should be repeated from the Site Baseline stage in order to reestablish the Optimized Baseline.