...
- it can improve responsiveness of the TeamCity server, as VCS-specific operations sometime require significant CPU and memory resources. If these operations are moved to a separate process, chances are main TeamCity server will work faster.
- VCS worker improves reliability of the server. Any bugs in a VCS-specific component will affect VCS worker but won't affect the worker, not the server. If there is a memory or resources leak, it can cause VCS worker failure, but the server will at least will be able to show the user interface, access builds, changes, etc.
- it should be easier to discover CPU and memory issues if they are related to VCS operations. Without the worker, if some VCS plugin ate eats a lot of resources it can be hard to find it, because the plugin works runs in the same Java process as server and server usually does a lot of work. With worker this should be easier.the (usually busy) server.
Currently worker supports the following operations:
...