QA (public) » openQA Project (public)

We right now schedule one limit_assets and one limit_results job for every ISO posted. Which was fine when all ISOs
posted were either TW or SLES builds - i.e. rarely.

But now we see dozens of incidents posted as ISO per hour - and the GRU is not able to run them as quickly. And fact is,
the actual task is a global one, so there is no need to do this more often than once in a while. We can't really decouple
it from the actual load, but binding it to ISO posts sounds wrong too.

Just brainstorming possibly solutions:

• keep binding it to ISO post, but make sure there is only one of such job around
• only trigger the task on every Xth job created (where X could be 1000 or generally configurable)

this is mildly urgent as I'm removing 1000 gru tasks daily from the backlog