We are extensively using tag change value script. Thoses script does a lot of thing and are very usefull because they can be coded in UDT. So when we create a new instance of a UDT, all the scripts are automaticly created.
Now the problem is when many tags change values at the same time, we experiment some lags in the script execution.
We look in the threads page and the is 3 threads that seem to execute all the change values script:
gateway-tags-eventscripts-3,
gateway-tags-eventscripts-2,
gateway-tags-eventscripts-1
Is there a way to increase the number of threads that are responsible to execute thoses scripts?
Add an override for ignition.tags.scriptthreads to the ignition.conf file, in the wrapper.java.additional settings, then restart the gateway. wrapper.java.additional.<x>=-Dignition.tags.scriptthreads=5
Try to keep the changes sane - giving yourself a hundred event script threads is not going to help performance, and is actually a terrible idea. There’s often a better way to structure things to avoid bogging the event executors down (ie, using async threads spawned from event scripts can be the better approach; it depends entirely on what these scripts are doing)
Finally we had to update our gateway to make it work. We were using 7.9.3 and now we use 7.9.9. I think it is impossible to have more than three threads until 7.9.5.