User guide

Viz Engine Administrator’s Guide

9 Shared Memory (SHM)

The information in this section relates to the VizCommunication.Map (see the Viz Artist

User Guide).

A local VizCommunication.Map in each Viz Engine (as part of a cluster), collects and

stores data. This data can be internal data, like a scene script pushing data to the map,

or data from external control applications through TCP or UDP.

This section contains information on the following topics:

• External Data Input

• Internal Data (Interactive Scene)

• Synchronization

• Snapshot

See Also

• Data Sharing (see the Viz Artist User Guide)

9.1 External Data Input

Data feed into the Shared Memory (SMM) should be done through the dedicated UDP

or TCP IP ports for the SMM. Vizrt provides a set of components, SendToSMM, to makes

this task easier.

Note: Go to <Viz Install Directory> -> Tools -> SendToSMM, for more information

about SendToSMM.

Data can also be sent to SHM through a Command Interface. Data sent through the

Command Interface may be seen as a good option because the data would need to be

sent to one Viz Engine only, and this Viz Engine engine would then distribute the data

to the other Viz Engines. But Data sent to SHM through the Command Interface has

problems:

• Data sent through the Command Interface will block the render queue of the

receiving engine causing potential frame drops. Since the data needs to be sent

through a command significant more bytes are transferred over the Network.

• This Viz Engine is also a single point of failure

• The data will arrive at this one Viz Engine sooner than on all other Viz Engines

• The notification method of the Viz Graphic Hub is used to distribute the data and

can cause additional load for the Viz Graphic Hub