Comment 4 for bug 618403

I had a poke at this a bit more today and I agree that adding the redundant not null clause is the best for now. It generally performs the best and most consistently across distro, distroseries, projects, project groups, etc. However, there are some combinations where I can't find a query to get below 300-400 ms. For now, that's okay, but the more quickly we drive down our timeout threshold, the more quickly this becomes a problem again.

We need to have a way to push this out of the web app. The jobs system broke down for us when used for heat before. Some of that could have been our use of it (firing off too many jobs or a job for every bug touched). But whatever we do, we need a way to defer this calculation only momentarily because of how much heat is used in the web UI now. i.e. we need to push this out of in-app calculation, but it still needs to happen pretty quickly so web pages are up to date.

I'm working on a branch now to make this minor query change, still leaving it in app, to buy us some time.

Cheers,
deryck