By Graham Mckendry-Oracle on Nov 19, 2014
As organizations continue to increase their volume of digital content, migrate business processes to software-driven frameworks, and expand the complexities of the underlying software/hardware architectures, system performance becomes an increasingly important success factor.
In the world of AutoVue, the most important aspect of performance is file load time – the time it takes from when the user clicks “Open” or “View in AutoVue” to when the file is displayed and the user can start working with it. There are many factors involved in file load time, including:
- Deployment architecture
- Specifications of each node
- Configuration of each node
- Network performance
- System load
A proactive approach to performance tuning requires expert understanding of the network and all involved nodes (e.g. load balancers, firewalls, proxy servers, application servers, DMS/PLM systems, AutoVue servers, client machines, etc) as well as load-testing prior to go-live. In addition to proactive planning, many customers identify the need to continue performance tuning after go-live, as the usage patterns evolve.
Dissecting the performance bottlenecks of file load time requires collecting various information including configuration settings and log files. In order to provide general guidelines for this process, our Support team authored a 2-part troubleshooting whitepaper which is published in the My Oracle Support knowledge base:
- Note 1595727.1 - AutoVue Client/Server Performance Troubleshooting Guide -Part I-
- Note 1605087.1 - AutoVue Client/Server Performance Troubleshooting Guide -Part II-
I highly recommend this read for any AutoVue admins and SIs interested in file load time performance analysis – whether it be during pre-go-live planning stages, or during ongoing system maintenance.