On 01/08/2012 07:53 PM, Dan Callaghan wrote:
Excerpts from Steven Lawrance's message of Mon Jan 09 10:36:48 +1000 2012:
Bill's concern is the time spent polling RHEV to check whether it has the resources, on top of the existing SQL query for "real" systems, once for each queued recipe, on each iteration of the loop (currently every 20 seconds).
That SQL query is already fairly expensive, but it doesn't really hurt. Is the call to RHEV to say "can you provision this recipe?" actually slower than that SQL query? (Can RHEV handle the load from such frequent requests?)
The difference is we're doing one sql command that joins the queued recipes to available systems. So even if you have thousands of queued recipes its still one sql call and you only get back a list that has work to be done.
We don't want to constantly process thousands of queued recipes, that's what the old rhts did.
Maybe we are worrying over nothing. Maybe adding lots of code in Beaker to track RHEV's available resources isn't really necessary?