Performance

Sierra++ is carefully designed so that the overhead on Sierra Chart and your computer is negligible.

Designed for stability and speed

Sierra++ study serves as a thin bridge between Sierra Chart and Sierra++ application.

It is active only when you send a command from Sierra++ application (change a color, add a study,…). When Sierra++ application is not running, or when it is idle, Sierra++ study is sleeping and does almost nothing.

It is not required to keep Sierra++ application running. Start it when you need to change a setting, then close it.

When it is running, Sierra++ application uses very little computing power. GPU load is tightly optimized.

Under the hood

Sierra++ application is coded in C++. The binary size is ~1MB, without any dependency or framework to load. It starts without any delay.

Every technical choice is made for usability while preserving CPU and memory usage, following design practices inspired from IoT / Embedded devices where RAM and CPU are very limited.

The communication layer between Sierra++ study and Sierra++ application can handle hundreds of charts, and transmit thousands of commands in a breeze.

My daily dev setup involves multiple chartbooks and hundreds of charts loaded in two Sierra Chart instances. With a mid-range 16GB i5 laptop, and a total number of charts varying from 10 to 250, time measurements from inside Sierra++ study indicate an average overhead of 0.1% of chart rendering time.

Responsiveness

As with other studies, Sierra++ study activity is controlled by Sierra Chart’s internal sequencer.

You typically won’t experience any significant delays, except when a chart is loading data. In such cases, wait until data is fully loaded.