Bug 1062480

Description of problem:

On large installations, the beakerd processing loops can be quite slow

Version-Release number of selected component (if applicable):


How reproducible:

Always on a large beaker installation

Steps to Reproduce:
1. Set the slow query log to log anything over 15 seconds
2. Queries from beakerd processing loops turn up there
3.

Actual results:

These kind of queries show up:

SELECT count(1) AS count_1 
FROM recipe_set INNER JOIN job ON job.id = recipe_set.job_id 
WHERE job.dirty_version = job.clean_version AND NOT (EXISTS (SELECT 1 
FROM recipe 
WHERE recipe_set.id = recipe.recipe_set_id AND recipe.status != 'Scheduled'));

Expected results:

Not to be there

Additional info:

A simple fix is to add job.deleted IS NULL to the WHERE clause. In my testing, that has brought down the query times from ~15-20 seconds to 4-6 seconds.