VCS polling performance - can I increase the # of threads to improve polling frequency across a large # of VCS roots?

I came across this post - https://teamcity-support.jetbrains.com/hc/en-us/community/posts/206221769-VCS-Executor-thread-pool-size-configuration - and wanted to confirm it is still accurate for TeamCity 10.0.4.

In my TeamCity install, we have ~ 530 VCS roots and a Default VCS changes check interval of 180s ... and we are seeing delays with builds being kicked off due to late polling.

In my teamcity-vcs.log, I am seeing thread names of the following patterns:

• [ical executor <int>]
• [cal executor <int>]
• [ executor <int>]

and wanted to confirm that creating an internal.properties file and setting the value of teamcity.threadpool.vcsexecutor.threads.max to some value > 10 was indeed the solution I was looking for.

If someone could confirm, that would be much appreciated.

We are independently looking at WebHooks as an option to reduce our polling load ... but have various issues to overcome on this front. So, in the meantime, we wanted to increase our overall polling performance to ensure builds are kicked off in a more timely fashion.

Thanks in advance,

-Tim