ZK Developer's Reference/Performance Monitoring

To improve the performance of an Ajax application, it is better to monitor the performance for identifying the bottleneck. Depending on the information you'd like to know, there are a few approaches.

• PerformanceMeter: Monitoring the performance from network speed, server-processing time and the client-rendering time.
• EventInterceptor: Monitoring the performance of each event listener.
• There are a lot of performance monitor tools, such as VisualVM and JProfiler. They could provide more insightful view of your application.

Performance Meter

PerformanceMeter is a collection of callbacks that the implementation could know when a request is sent, arrives and is processed.

As show above, T1-T5 identifies the following callbacks.

• T1: PerformanceMeter.requestStartAtClient (String, Execution, long)
• T2: PerformanceMeter.requestStartAtServer(String, Execution, long)
• T3: PerformanceMeter.requestCompleteAtServer(String, Execution, long)
• T4: PerformanceMeter.requestReceiveAtClient(String, Execution, long)
• T5: PerformanceMeter.requestCompleteAtClient(String, Execution, long)

Thus,

• Server Execution Time: T3 - T2
• Client Execution Time: T5 - T4
• Network Latency Time: (T4 - T3) + (T2 - T1)

Notice that, when we make a connection to load a page for the first time, only Server Execution Time is available. T4 and T5 will be saved on the client side, and sent back along with the next request.

Once implemented, you could register it by specifying the following in WEB-INF/zk.xml (assume the class is called foo.MyMeter):

<zk>
    <listener>
        <listener-class>foo.MyMeter</listener-class>
    </listener>
</zk>

Further Reading

For sample implementations, you might take a look at the following articles:

• Performance Monitoring of ZK Applicaiton
• A ZK Performance Monitor
• Real-time Performance Monitoring of Ajax Event Handlers

Version History

Version	Date	Content