Performance considerations

• Touchstone will continue to operate with cores as part of the analysis server/compute node so that you can leverage your existing systems.
• For installations that include both Touchstone and Touchstone Re:
  • Both applications must use the same version of the SQL server.
  • You may adjust requirements based on expected usage patterns. Please work with your technical representatives to configure the most optimal setup for your business needs.
• As with every release, overall disk space requirements typically increase when you run previous model versions and new model updates at the same time.
• You may also see an increase in the size of the Result database if you run detailed loss analyses with new options to save results and YELT[s]¹ by secondary sub-perils.
• Installations are designed to be run in an English-language environment. This includes operating systems and SQL servers.

Your installation may have different requirements and some portfolio sizes may need larger configurations. Feel free to contact the Technical Services Group for more information. Other considerations include:

• Machine names must be uppercase for all machines running Touchstone and Touchstone Re.
• For an in-place upgrade: To retain the historical analysis log files, back up all the folders/files under {Install Directory}:\Program Files\AIR\Work\OutputManagement.
• All model files should be installed on the model share rather than on the local drive for space considerations.
• The recommended ratio is one model share for every 32 compute cores.
• SSAS (SQL Server Analysis Services) must be installed in multi-dimensional mode for Touchstone installations.
• Clients that license APIs must run the head node and the Application Server on separate servers.
• Due to the complexity of the model, Verisk recommends running each Verisk Severe Thunderstorm Model for the United States analysis in Touchstone one at a time.
• Once installation is complete, inspect and review the installation log files on each node for any errors under C:\Program Files\AIR\Logs.