| << Back to previous view |
|
[QB-4163] Ability to Manually Set Node Benchmark via Setting in node.properties
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 15.0.5 |
| Fix Version/s: | 15.0.9 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Ali Haider | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Within our Quickbuild Agents Pool we have setup many Virtual Machines with different hardware specifications. Some VMs have newer CPUs and newer hypervisor versions, while others are running on older iterations. As a result, we have seen that our build times can vary upwards to 30 minutes based on the Agent that picks up a request from the queue.
Since we know which Agents will always produce the fastest build, we would like for a way to prioritize them for every execution. Ideally, they are the first to pickup an incoming job, followed by any number of groups of older agents. In discussion, we wanted to know if it would be possible for us to manually set the Node Benchmark rather than calculating it via scripts that may not always generate the most accurate results. Thanks, Ali Haider |
| Comments |
| Comment by Robin Shen [ 19/Mar/25 11:06 PM ] |
| When manually specifying a benchmark, if some builds are already running on fast agents, should subsequent builds be moved to slow agents, or is it better to let them queue for fast agents? |
| Comment by Albert Mika [ 20/Mar/25 08:03 AM ] |
|
By defining static node benchmark value in node.properties we just want to prioritize fast performing agents (based on our judgement and hardware specification) over slower ones.
Other aspects should left intact. Responding directly: if fast agents are busy let slower ones be assigned to newly requested builds. We do not want to build any queues. |