Best Practices

Browser Support

There have been noticeable issues in rendering large charts (near full-screen size) in Firefox and as such Streamline does not recommend it's use with this product at this time until a suitable work-around can be found. This is a known firefox issue with rendering large HTML canvas elements.

SC Charts performs incredibly well in chromium based browsers such as Google Chrome, Microsoft Edge, and even the Ignition Designer.

Installation

Installation is as easy as any other Ignition module. Simply navigate to the module installation page within your gateway web browser, install the downloaded file, accept the certificate, and enjoy!

Upgrading

It is recommended to uninstall the previous version of the module before upgrading. All views which were previously configured will retain their props but may require additional configuration should there be breaking changes between versions. All designer sessions should also be closed prior to a version upgrade to ensure all caches are cleared. All version release notes are detailed in Releases.

Minimum Requirements

WASM based charting does utilize additional memory to achieve lightning fast rendering and as such Streamline recommends the use of the following minimum requirements for a seamless development experience. These suggestions are not strict but they do provide additional safety buffering to ensure you can meet your clients needs. Also note that these requirements are based on datasets of 150000 rows (with >3 columns) or larger, basic hardware may be acceptable for more typically sized datasets.

Ignition Server

Host RAM: >16 GB

Gateway Memory: 8192 MB

Developers

Host RAM: >16 GB

Designer Memory: 2048-4096 MB

Perspective Clients

Host RAM: >8 GB

Pushing Ignition's Limits

By default, the perspective websocket has a maximum message size of 2 MB this value can easily be exceeded when attempting to load large datasets into perspective views. Adding the following line to the Ignition gateway ignition.conf file can increase the maximum websocket message size:

Example: wrapper.java.additional.7=-Dperspective.websocket.max-message-size=65536 (64 MB)

Increasing the websocket message size to allow for larger datasets will increase data transfer over the network, users should be especially cautious when using this feature with mobile views as carrier data rates may vary and apply. Unexpected behavior is also expected as dataset sizes increase as not all client machines will meet the specifications to handle the memory increase.