Improving InDesign Server performance in Studio Server 10.10 by storing files locally instead of on a file share

Info: Performing the step described in this article requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. When Studio Server is running in WoodWing Cloud, these steps are managed by WoodWing. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.

When InDesign Server is used for generating layout previews (for example for the Print editor of Studio), performance is very important.

The layout preview is generated as a JPEG file and is stored in the WebEdit folder of Studio Server.

Configuring the location of the WebEdit folder is done via the WEBEDITDIR setting in the configserver.php file of Studio Server.

Choosing the location of this folder has a large impact on performance:

• Locally on the same drive as InDesign Server. This results in the best performance and stability. We therefore highly recommend to use this configuration.

Note: There is one downside to this method: it is not possible to have multiple (physical) InDesign Server machines connected. This is because only one WebEdit folder can be defined in Studio Server.

• Remotely on a file share, for instance where the file store is kept. This is the default configuration of Studio Server.

Note: When storing the WebEdit folder remotely on a file share, the location where Studio for InDesign and InCopy stores its files (the smartconnection.noindex folder) will also be on that file share. To improve performance, the smartconnection.noindex folder can be made local to InDesign Server by using the UseCustomBaseFolder option and setting it to a local folder. This way, at least part of the file access actions become local resulting in more stability and better performance.