Concurrent execution...?
Posted: Thu Sep 05, 2019 9:58 pm
Hi everyone
I'm trying to squeeze as much performance as possible out of a flow containing multiple copies of a script element that is set to concurrent usage.
In previous versions of Switch running an Unlimited Performance Module, I was able to spawn dozens of instances of a script set for concurrent usage whereas in the current versions (2019 and 2018 update 3 with an Unlimited Performance Module that is properly licensed and activated) I'm lucky to get three or four instances.
My concurrent processing preference is set to 50 to be conservative and the Windows systems this flow is running on are pretty beefy in terms of CPU and RAM.
If anyone has any feedback or recommendations, I'd be most appreciative.
Thanks.
William Buckingham
I'm trying to squeeze as much performance as possible out of a flow containing multiple copies of a script element that is set to concurrent usage.
In previous versions of Switch running an Unlimited Performance Module, I was able to spawn dozens of instances of a script set for concurrent usage whereas in the current versions (2019 and 2018 update 3 with an Unlimited Performance Module that is properly licensed and activated) I'm lucky to get three or four instances.
My concurrent processing preference is set to 50 to be conservative and the Windows systems this flow is running on are pretty beefy in terms of CPU and RAM.
If anyone has any feedback or recommendations, I'd be most appreciative.
Thanks.
William Buckingham