[tools][EPIC] Scheduling redesign
Currently we are scheduling using DB with specific crafted query with the ORM - which is a consuming process both in terms of CPU and memory, even refining furthermore the query could be in long-term a dead end, and being problematic as we might have more requirements from it.
This ticket is meant just as a tracker to group refactorization/enhancements, redesign proposals.
#1 Updated by EDiGiacinto over 4 years ago
My 2c With regards to replacing DB, and doing it in memory - if AMQP is not a way to go (so, that means also dispatching jobs over ws would be replaced) - i would explore the possibility to switch to a SAT solving mechanism instead, avoiding to hard-code condition ourselves in the future. As i see it, we can re-formulate our problem as conditions that can be nicely expressed in CNF.
#6 Updated by EDiGiacinto over 4 years ago
Don't! The problem is way too simple for such a monster solution
Well, it seems growing in complexity now, so maybe a simple solution is not enough anymore - and it might actually help slim the logic, as we could infer CNFs from job settings.
Not saying that is the road to hit - just worth mentioning the possibilities.
#17 Updated by szarate over 1 year ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html