System Lag DThinkScriptCalculatingPool

[Glefdar]

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.

 

[MerryDay]

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.

https://usethinkscript.com/threads/thinkorswim-app-system-lag.1173/#post-50764

 

[Arrive8848]

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.

This setting is in the vmoptions file, which each instance uses when it starts up. So therefore, if you run concurrent instances, you should specify your total virtual cores / instances. For example:

Total virtual cores: 16 (ex. 8 cores w/ hyperthreading)
Concurrent instances: 8
DThinkScriptCalculatingPool: 2 (16 / 8)

I'm running two ToS instances on my 20c/40vc Linux workstation and will be testing the impact of setting DThinkScriptCalculatingPool to 20, before I test running more concurrent instances. I'll report my findings.

 

[Glefdar]

This setting is in the vmoptions file, which each instance uses when it starts up. So therefore, if you run concurrent instances, you should specify your total virtual cores / instances. For example:

Total virtual cores: 16 (ex. 8 cores w/ hyperthreading)
Concurrent instances: 8
DThinkScriptCalculatingPool: 2 (16 / 8)

I'm running two ToS instances on my 20c/40vc Linux workstation and will be testing the impact of setting DThinkScriptCalculatingPool to 20, before I test running more concurrent instances. I'll report my findings.

It would be great if you’re able to determine more details about how this parameter should be used. Please keep us updated!