Score:0

Varying, exclusive limits on concurrency in GitLab runner

ca flag

I have a Linux server used as a GitLab runner. I'd like the server to be usable for two different purposes simultaneously:

  1. For build jobs, unit tests, etc. (things that aren't timing sensitive) many jobs can be run concurrently to take advantage of the memory availability of the system and make better use of the CPU while some jobs are doing I/O-bound activities like downloading dependencies.

  2. When a timing-sensitive job (a performance test) is being run, no other build jobs etc. should be running because if they're competing for system resources the test results won't be comparable between runs.

Is there a way to set up a GitLab runner config.toml in a way that jobs of type 1 can run concurrently but the jobs of type 2 are guaranteed to be run without any other jobs going on at the same time?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.