Two terminals, one machine, and the surprises
Posted: Fri Oct 30, 2026 10:23 am
Two terminals, one machine, and the surprises
Running two or three terminals on the same computer is common. Different brokers, different strategies. It works. It also introduces interactions.
Shared resources are the first issue. CPU, memory, and network bandwidth are split. A busy terminal can slow the others.
Another is file collisions. If terminals share a data folder or a log file by accident, errors follow. Portable installations with separate folders avoid this.
A less obvious point is timing. Starting several terminals at once produces a burst of data downloads that can slow everything for several minutes.
For critical strategies, dedicating a machine or at least a separate virtual instance to each terminal removes the cross-effects.
There is also a licence and login angle. Some brokers limit simultaneous sessions per account, and starting a second terminal with the same login can knock the first one offline without any warning on screen. That alone has caused more than one open position to go unmanaged. Checking the broker's rules on concurrent connections takes a minute and avoids the surprise.
Has the performance of one terminal ever dropped because of activity in another on the same machine?
Running two or three terminals on the same computer is common. Different brokers, different strategies. It works. It also introduces interactions.
Shared resources are the first issue. CPU, memory, and network bandwidth are split. A busy terminal can slow the others.
Another is file collisions. If terminals share a data folder or a log file by accident, errors follow. Portable installations with separate folders avoid this.
A less obvious point is timing. Starting several terminals at once produces a burst of data downloads that can slow everything for several minutes.
For critical strategies, dedicating a machine or at least a separate virtual instance to each terminal removes the cross-effects.
There is also a licence and login angle. Some brokers limit simultaneous sessions per account, and starting a second terminal with the same login can knock the first one offline without any warning on screen. That alone has caused more than one open position to go unmanaged. Checking the broker's rules on concurrent connections takes a minute and avoids the surprise.
Has the performance of one terminal ever dropped because of activity in another on the same machine?