Has anyone ever checked if vmoptions parameter “DThinkScriptCalculatingPool” evenly distributes load across multiple TOS instances?
The vmoptions file for the TOS executable can have a parameter added “-DThinkScriptCalculatingPool=16” where 16 is the number of cores your CPU has.
I’ve read that this parameter allows the application to run more efficiently.
However, it’s unclear if the value needs to be divided for the number of TOS installations that are running simultaneously.
If I have 8 TOS installations running, should this value be set to 2 in each vmoptions file or should it be kept at 16 because the application is going to evenly distribute the load?
I asked this question in one of the ThinkOrSwim support chat rooms and didn’t receive any clarity. So I’m wondering if anyone has benchmarked this before.
The vmoptions file for the TOS executable can have a parameter added “-DThinkScriptCalculatingPool=16” where 16 is the number of cores your CPU has.
I’ve read that this parameter allows the application to run more efficiently.
However, it’s unclear if the value needs to be divided for the number of TOS installations that are running simultaneously.
If I have 8 TOS installations running, should this value be set to 2 in each vmoptions file or should it be kept at 16 because the application is going to evenly distribute the load?
I asked this question in one of the ThinkOrSwim support chat rooms and didn’t receive any clarity. So I’m wondering if anyone has benchmarked this before.
Last edited by a moderator: