Workbook performance can be improved by:
The IDE refreshes all views in the workbook with updated information from the codestore after a build. The workbook maintains the views on every page in the workbook, even the views that were previously displayed in panes. The number of views maintained has a direct effect on the time it takes to refresh. You can reduce this time by discarding undisplayed views. Page descriptions are saved before the views are discarded, so when you click a page button for a page containing discarded views, the views are re-created and displayed.
The codestore read lock timeout value controls the amount of time the IDE waits when it queries the codestore for information to display a menu containing codestore objects, or to change the object flowing on a link. If you set the timeout value lower than the 2000 millisecond default, the IDE abandons the query sooner and displays whatever information it received from the query. The timeout value can be changed using the Settings view in the Workbook section.
It takes time to save the codestore to disk. To improve performance, you can limit how often the codestore is saved using the Settings view in the Workbook section:
Regardless of the above settings, the codestore is always saved to disk after the initial build of a project, and when the IDE is closed. If for some reason, such as a system failure, the codestore is not saved to disk before the transient codestore is erased, your next build will be based on the most recently saved codestore.
