After reading about the benchmark plugin on the jetbrains blog, I immediatly had to test it on my testing/staging instance. The test results where of course rather ... optimistic ... but nontheless interesting. Now my question is, if it would be possible to take this test further:
1.) Produce log and test results on a different machine, this way I can also test if my network interface is holding up, not just cpu, memory and disk. If I could, for example start two instances of TC, both using the same plugin, but one contains the build configurtion, while the other one hosts the virtual agents, traffic would have to flow via my actual network. Alternatively, if the agent part could be run in its own JVM, without the help of a separate TC instance it would be even better.
2.) Run continuesly - Currently the plugin creates all build configurations, all agents, starts the job everywhere and then starts sending logs and deletes everything afterwards. If instead agents and build configurations would stick around a bit, it would be possible to also see if the Queue can handle that many jobs and agents without issue. As in, keep creating many jobs, getting consumed by the virtual agents in parallel to handling the load.
Is there any ongoing support going to happen, or is the source available for extra experiments?