RAM and the terminal that eats it

[Fairman]

RAM and the terminal that eats it

A trading platform keeps price data for every open chart in memory. Open dozens of charts with a long history, and memory consumption climbs into the gigabytes. Running several terminals on one machine multiplies it.

When physical memory runs short, Windows starts swapping to disk. The platform slows, the interface hesitates, and a burst of ticks produces a queue of delayed actions.

Memory leaks add to the issue. Some expert advisors or indicators allocate memory and never release it. A terminal that runs fine in the morning is sluggish by evening, and a restart cures it.

Signs to watch: memory usage in the task manager that grows steadily during the day, or a platform that needs a daily restart to stay responsive.

Practical steps include limiting the maximum bars on a chart to what's needed, closing unused charts, and monitoring each terminal's memory figure.

For a VPS, memory is often the first limit hit. A plan with 2 GB may run one terminal comfortably and struggle with three.

Adding RAM is among the cheapest ways to improve stability, and often the least considered.

After a full day of running, how much memory does the terminal use?