|
|
|
The system log already shows where the step for certain configuration is running. Or you can write a script looping all configurations to check its step node match setting. Also please make sure to upgrade to latest QB version as it solves a problem of UI sluggish when some problematic agent is connecting to QB server.
Latest version improved the UI a lot for large number of configurations and builds.
|
So instead of guessing the load, we'd like to check why the UI is slaggish. Firstable, please make sure that all your builds are set to run on agents instead of server (this can be done by dispatching master step of the build to agent), then please turn off auto-refresh of the UI (by specifying auto refresh interval as 0 in system setting).
Also is the UI always slaggish or is it happening occasionally?