Contents:

1. Use multiple instances with different chart update settings

Great way to distribute processing load. Instead of jamming all into one, multiple instances are created which maintain their own copies of chartbooks, settings, and chart data.

Official Sierra Chart Documentation Here:

Using DTC Server for Data and Trading in Another Sierra Chart Instance

• Open Sierra Chart
• Create new instance by selecting File > New Instance from the title bar
• Dedicate 1 instance for lower latency updates, the other(s) for lower latency (Easier with multiple computer monitors)
  • First change the default update interval for each instance: Global Settings > General Settings > Chart Update Interval in Milliseconds. Ex. 100 for instance 1 trigger charts, 800 for the other instance for slower updates
  • Next change the interval on indiciducal charts. Click the chart > Chart Settings > [*Display] > Chart Update Interval in Milliseconds. Ex. 100 for trigger chart

Tip: To open all instances on startup go to Global Settings > General Settings > Instances to Run on Startup. 2,3,4 etc

2. Lower the Days to Load data for every chart possible

For each chart in a chartbook, only select the neccessary days to load. Keep in mind if you have studies that use older data they will not function correctly if the required data exceeds the days loaded value. Ex. The Previous Week Hi will not show on charts if the days loaded is only 2 days.

The more days that are loaded on each chart the longer the start-up time. Use the absolute minimum.

3. Only display necessary charts, and minimize or hide all others

Every chart that is open or even collecting data should have a purpose. Minimize all low visual priority charts. To disable the graphics of the chart reducing CPU load:

• Title Bar: Window > Hide Window

4. Set Chart Update Interval to the slowest possible times