Last updated on FEBRUARY 15, 2017
Applies to:Oracle AutoVue Office - Version 20.0.0 and later
Oracle AutoVue 2D Professional - Version 20.0.0 and later
Oracle AutoVue 3D Professional Advanced - Version 20.0.0 and later
Oracle AutoVue EDA Professional - Version 20.0.0 and later
Oracle AutoVue Electro-Mechanical Professional - Version 20.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 14-14-2014***
The overall file-load time in AutoVue Client/Server Deployment is comprised of various performance factors. This article discusses the details around optimizing two of these performance factors, namely:
- The time required to load the Java Virtual Machine (JVM)
- The time required to load the JVue applet in the client’s browser
The optimization essentially involves pre-loading both the JVM and the JVue applet before they are required by the user. This way, when the user does eventually decide to view a file in AutoVue, the JVM is already loaded on their client and the JVue applet is already initialized and connected to the AutoVue server.
AutoVue server administrators.
When is this optimization feasible?
The potential for these particular performance gains depends on the way your users launch AutoVue. In order to pre-load the JVM and the JVue applet, the users must already be browsing another webpage prior to launching the applet webpage. The most common example would be a user browsing files in a web-based DMS/PLM/ERP/ECM; while the user browses the repository, a hidden JVue applet is initialized in the background.
When is this optimization beneficial?
This depends on the environment and the usage scenario. Many clients now have Sun’s “Java Quick Starter Service” (this is abolished from Java 8) running by default, which already speeds up the load time of applets. In addition, in many environments the client already has the JVM loaded by the time they want to view a file in AutoVue – for example if the JVM gets loaded for other purposes when browsing the DMS/PLM/ERP/ECM. Therefore, the scenarios where this optimization tends to actually show notable performance gains include:
- Environments where the AutoVue client-server connection typically takes a long time to establish, for example a client in New York connecting to a server in Paris
- Use-cases where users are opening small file sizes and performing quick processing before closing the file, and perhaps only opening a single file in AutoVue during a given session. In these cases, you do not want the bulk of the user’s AutoVue usage to be waiting for the applet to load and connect to the server.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms