Better schedule builds among agents #324

New issue

Open

opened 2022-12-28 11:14:23 +01:00 by Jef Roosens · 0 comments

Jef Roosens commented

2022-12-28 11:14:23 +01:00

Owner

This idea just popped into my head, gonna dump it here.

What if each agent registered itself with the server on startup, providing the server with the agent's polling frequency, amount of allowed builds, and a unique identifier (uuid for example), along with some metrics on how powerful the agent is.

These values could then be used by the server to better schedule the builds among agents (e.g. if it knows 5 agents are polling and 5 jobs are waiting, it'll spread those among those 5 agents). Heavier jobs could also be scheduled on more powerful agents, or agents with fewer running jobs etc, I think there's a lot of potential here, all without having to convert to a persistent connection-based system.

This idea just popped into my head, gonna dump it here. What if each agent registered itself with the server on startup, providing the server with the agent's polling frequency, amount of allowed builds, and a unique identifier (uuid for example), along with some metrics on how powerful the agent is. These values could then be used by the server to better schedule the builds among agents (e.g. if it knows 5 agents are polling and 5 jobs are waiting, it'll spread those among those 5 agents). Heavier jobs could also be scheduled on more powerful agents, or agents with fewer running jobs etc, I think there's a lot of potential here, all without having to convert to a persistent connection-based system.