2018.1

l
Use efficient selectors. Using very precise selectors in scripts will be much faster than
using a text selector, especially on large documents. See "Use an ID as selector" on
page336.
l
Optimize your scripts. Custom scripts with non-optimized loops and unnecessary DOM
manipulations can slow down Content Creation. Use the Designer's test facilities to find
out which scripts can be improved (see "Testing scripts" on page332 and "Optimizing
scripts" on page336).
l
Only run the necessary scripts. Normally the Designer will run all scripts for each and
every record and section. You can save time in the process of Content Creation by
organizing scripts in folders, setting their execution scope or even disabling them (see
"Managing scripts" on page329). Note that loading a JavaScript library is generally very
fast and only done once for the record set.
l
Use a fast network and internet connection or avoid loading external or internet
resources. Using images, JavaScript or CSS resources located on a slow network or on a
slow internet connection will obviously lead to a loss of speed. While we do our best for
caching, a document with 5,000 records which queries a page that takes 1 second to
return a different image each time will, naturally, slow output generation down by up to 83
minutes.
l
Make sure to use optimized graphic resources. For instance, avoid using images with
transparency where no transparency is needed.
Hardware configuration
When processing speed is important, the following is suggested before looking into
Performance Packs to enhance performance.
l
Consider using a physical machine instead of a virtual machine. When running on a
Virtual Machine, the machine may report that it has sufficient hardware (cores) available,
but in a virtual environment you need to make sure that this hardware is not being shared
with lots of other virtual machines.
l For both virtual and non-virtual environments, make sure the machine is not busy with all
kinds of other processes.
l
Antivirus exclusions. Sometimes, virus scanners, other security software or indexing
services can interfere. It can help to disable those kinds of tools for the areas where
Connect stores intermediate files. You could exclude the entire
C:\Users\<connectuser>\Connect folder. See also: "Antivirus Exclusions" on
page15.
Page 30