Performance Monitoring"
From Documentation
| (16 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
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. | 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. | ||
| − | * <javadoc type="interface">org.zkoss.zk.ui.util.PerformanceMeter</javadoc>: Monitoring the performance from network speed, server-processing time and the client-rendering time. | + | * <javadoc type="interface">org.zkoss.zk.ui.util.PerformanceMeter</javadoc>: Monitoring the performance from the network speed, server-processing time and the client-rendering time. |
* <javadoc type="interface">org.zkoss.zk.ui.util.EventInterceptor</javadoc>: Monitoring the performance of each event listener. | * <javadoc type="interface">org.zkoss.zk.ui.util.EventInterceptor</javadoc>: Monitoring the performance of each event listener. | ||
| − | * There are a lot of performance monitor tools, such as [https://visualvm. | + | * <javadoc type="interface">org.zkoss.zk.ui.util.Monitor</javadoc>: Monitoring the number of desktops, sessions and other system load. |
| + | * There are a lot of performance monitor tools, such as [https://visualvm.github.io/ VisualVM] and [http://www.ej-technologies.com/products/jprofiler/overview.html JProfiler]. They can provide more insightful view of your application. | ||
| − | + | {{ZKDevelopersReferenceHeadingToc}} | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
For sample implementations, you might take a look at the following articles: | For sample implementations, you might take a look at the following articles: | ||
| Line 38: | Line 17: | ||
* [[Small Talks/2010/January/A ZK Performance Monitor|A ZK Performance Monitor]] | * [[Small Talks/2010/January/A ZK Performance Monitor|A ZK Performance Monitor]] | ||
* [[Small Talks/2010/April/Real-time Performance Monitoring of Ajax Event Handlers|Real-time Performance Monitoring of Ajax Event Handlers]] | * [[Small Talks/2010/April/Real-time Performance Monitoring of Ajax Event Handlers|Real-time Performance Monitoring of Ajax Event Handlers]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
{{ZKDevelopersReferencePageFooter}} | {{ZKDevelopersReferencePageFooter}} | ||
Latest revision as of 07:08, 11 November 2020
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 the network speed, server-processing time and the client-rendering time.
- EventInterceptor: Monitoring the performance of each event listener.
- Monitor: Monitoring the number of desktops, sessions and other system load.
- There are a lot of performance monitor tools, such as VisualVM and JProfiler. They can provide more insightful view of your application.
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