Troubleshooting: Tips for Streaming Data - Intergraph Smart Review - Help

Intergraph Smart Review Help

Language
English
Product
Intergraph Smart Review
Search by Category
Help
SmartPlant Foundation / SDx Version
7.1 (2018 R1)
Smart Review Version
13.x(2018)

SVF Project Files

Break up model data by proximity (location) and create smaller VUE files to improve streaming. Also, each separate visual entity should be a separate graphic object in the authoring environment.

Determine Packet Sizes for Publishing

Streaming data is sent in packets of data. The number of packets of data sent increases with smaller packet sizes and decreases with larger packet sizes. When streaming the whole model, larger packet sizes are desirable because fewer packets are sent, which reduces the total streaming time. When streaming just a subset of the model, smaller packet sizes are desirable because less of the model is sent in each packet and you may see your requested data faster, if it fits within the smaller packets.

For PDS publishing of streaming VUE file data over a slower connection, this packet size range can be reduced. To improve total throughput on faster LAN connections, then the recommended packet sizes are 510000 and 512000. You can experiment with different packet sizes on your network to determine the best results for your purposes.

  • When publishing using the PDS Loader, use Smart Review to set up your project view settings before publishing the project.

  • Undo any Smart Review project display set moves before publishing the PDS data to prevent locate problems with the published data.

Cache Streaming Data

To improve performance, use caching so that the View in SmartPlant Review and View Item in SmartPlant Review commands retain the model on the SmartPlant Foundation client and use the local cached model when the same model is displayed again.

  1. Specify the cache location for the SmartPlant Foundation Desktop Client by setting the Streamed3DModelCache value in the Settings.xml file (stored by default on the client machine in C:\Documents and Settings\<USERNAME>\Application Data\SmartPlant\Foundation\1.0). The following example sets the cache to the folder D:\cache.

    <configuration>
    <ProductDirectory>c:\Program Files\SmartPlant\Foundation\3.7\SPFDesktopClient\CurrentVersion</ProductDirectory>
    <datasheets dir="C:\" />
    <servers selected="spfserver">
    <server name="spfserver" host="spfserver" dir="spfasp" />
    </servers>
    <Streamed3DModelCache>D:\cache</Streamed3DModelCache>
    </configuration>

  2. Specify the cache location by setting the Streamed3DModelCache variable in the Settings.js file (stored by default on the SmartPlant Foundation server in C:\Program Files\SmartPlant\Foundation\1.0\SPFAsp\WebClient\Navigation and Reporting). The following example sets the cache to the folder D:\cache.

    var Streamed3DModelCache = "D:\\cache";

Acceptable Values for the Streamed3DModelCache Setting

"" (null string)

Specifies that Smart Review should use the Temporary Internet Files folder on the client computer for the cache. The user is responsible for cleaning this cache using Internet Explorer.

"none"

Indicates that no caching is to take place. Models are always retrieved over the network to the client computer.

<client folder>

Assumed to be a client folder that is used to cache the 3D models if the setting is anything other than "none" or null. You are responsible for cleaning the cache at your own discretion.

No value provided

Uses the Temporary Internet Files folder is used for the cache. If a location is specified, that folder and path must exist on each client machine, and you must use double slashes (\\) in the definition. If the defined directory does not exist on a client machine, the Temporary Internet Files folder is used.

Using the Temporary Internet Files folder (default) results in a server request per packet during streaming, even when the data is already cached. If this server request is not needed (due to slow server connections), then you should use a client folder for the cache instead.