Limiting the number of Trigger Check threads
Hello,
I'm trying to optimize our Teamcity Enterprise instance.
We rely highly on the "Maven Snapshot Dependencies Trigger" to determine if a parent project has been compiled to trigger the childs.
Doing a threads dump, I noticed I had about 150 "Async trigger check" performing source check or Maven check. This put a lot of load on both Teamcity and Nexus due to the amount artifact fetched.
Is the amount of thread used for trigger configurable? Is the trigger queue accessible in order to monitor it and determine an appropriate value ?
Thanks,
Philippe Busque
Please sign in to leave a comment.
Hi Philippe,
thanks for your report. How many Maven triggers do you have set up in your server?
Hi Denis.
I couldn't find where in the database this info was stored, but from the number of project that use them I would say roughly a thousand.
Each of those project pooling roughly 3-6 snapshot artifacts from the repository.
Hi Philippe,
thanks for the answer. I'm going to ask internally about this because the number seems huge, but wanted just to leave this here for you to know. Project and build configurations aren't stored in the database, they are stored in the data directory, under /config/projects in the form of XML files. Once you get there the structure is likely to be pretty obvious.