Kbase 18189: Things to consider troublshooting Apptivity applet load time
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/13/1998 |
|
Things to consider troublshooting Apptivity applet load time
There are two components to the length of time it takes an Apptivity
applet to load -- one is the amount of time it takes to download
classes to the client (keep in mind that classes are only downloaded
as needed).
To reduce the time it takes to download classes the classes can be
packaged in CAB or JAR files. (For more information see the file
deploy.html (and supporting HTML sample files) in the redist
directory under the Apptivity installation directory.
Additionally it is possible to store the CAB and JAR files on the
client so that they do not need to be downloaded each time. Refer
to the kbase entry "Apptivity FAQ How to cache CAB JAR files
locally on client" for more information.
The other component is the time it takes to initialize datasources.
One way to reduce datasource initialization time is to turn off
"execute query on startup" for as many datasources as possible.
Datasources which are not executed at startup then need to be
initialized programmatically by calling setFilter() or refresh().
Other things which contribute to performance of the queries at
startup have to do with the queries being performed, whether
the database is designed with indexes which are optimal for
those queries, and whether ODBC or JDBC is being used
to access the database. JDBC is preferred.
All of these factors and solutions should be considered to address
applet startup performance issues.
UTF 8/13/98 Apptivity 2.1