Support Board
Date/Time: Tue, 22 Apr 2025 06:12:07 +0000
Post From: v2734 : Forbidding external launch of sub-instances
| [2025-01-21 22:02:35] |
| Sébastien - Posts: 58 |
|
Hi Support, I updated to v2734 today and noticed that it isn't allowed anymore to launch a sub-instance using its Sierrachart_64.exe file. It is now obligatory to use File > New Instance. This restriction is a little bit inconveignant because it doesn't allow to use a script like this one to launch an instance of SierraChart on a specific CPU core with a High Priority. C:\Windows\System32\cmd.exe /c start "SierraChart 1" /High /affinity 2010 "E:\SierraChart\SierraChart_64.exe"
C:\Windows\System32\cmd.exe /c start "SierraChart 2" /High /affinity 1020 "E:\SierraChart\SierraChartInstance_2\SierraChart_64.exe" C:\Windows\System32\cmd.exe /c start "SierraChart 3" /High /affinity 802 "E:\SierraChart\SierraChartInstance_3\SierraChart_64.exe" Now the only way to do this is to manually set the target CPU core and Priority in the Task Manager at each startup... for each instances... which is not time efficient. If I don't do it, Windows is stacking 2 or 3 instances on a single CPU core, which I don't like at all because it becomes overloaded. It also sometimes launches Sierrachart on a Efficient core instead of a Performance core... not good. I'm sure you restricted the launch of a sub-instance for a good reason, but is there a way to still allow this kind of script to work ? Or to add a parameter inside Sierrachart to allow the users to chose which CPU core we want to use for each instance ? Regards, |