When a user launches a Nexaweb application, Nexaweb loads the client files onto the user system from the server. How you chose to develop your application determines how much of the application resources reside on the client solely and how much on the server.
Application performance is largely affected by the size and number of application files traveling between the server and client.
To optimize application performance, you need to determine a balance between:
To maximize the performance in either of these areas, you need to determine when to send application files from the server to the client.
To improve overall application performance you can pre-load many Nexaweb application files during application launch. Although pre-loading files slows the application launch, it speeds up the performance of the application later by reducing the amount of network traffic. Still, improving application performance does not mean that you have to sacrifice startup performance as there are methods for improving startup performance even if you pre-load more application files.
Generally, to improve:
The following table lists the specific resources that should be considered when trying to optimize performance.
File Types | Action |
MCOs | Compress into Jar files and place on the client classpath. |
Nexaweb Plugins | Compress plug-in JARs using pack200 and |
Custom plugins | Compress custom plug-in JARs using pack200 and |
Widget Images | These are the images that pertain to Nexaweb UI Compress in a Jar file and place on the classpath. Change references in XAL files to classpath references |
Custom Images | Compress in a Jar file and place on the classpath. Change references in XAL files to classpath references |
Overriding the JVM init sequence |
To optimize client loading, consider which classes to pre-load during initialization and which to load dynamically, when needed.
To optimize class loading, generally, pre-load classes required for your application's welcome page and for the first actions you expect the application users to perform from there. Load other classes dynamically, as needed. The number of classes you load at initialization may slow application start, but increase application performance afterwards.
The Nexaweb startup occurs as follows:
See the following topic for details on how to optimize client start-up.
To improve application performance in addition to the files you pre-load for application start-up you can pre-load the following types of files:
See the following topic for details on how to optimize overall application performance.
This topic,provides instructions on how to assess the load-time performance of an existing application.
In addition:
To inspect what gets loaded to the client when an application runs, you can run the application though a TCP/IP tunnel. This shows exactly how many requests are being made and which resources the client requests.
|