Comment 7 for bug 588684

{{{
11:02 < stub> noodles775: So that build page that was timing out. Does this query provide all the information we need for the bits that are timing out? http://paste.ubuntu.com/444495/
11:13 < noodles775> stub: checking
11:14 < stub> noodles775: Things also run more than twice as fast on a slave node (that particular query takes just over 5 seconds on the master, but 1.4 seconds on a slave). I don't think anyone will care if the stats are maybe a few seconds out of date.
...
11:21 < noodles775> stub: great, so I can update the storm code to (1) run on the slave and (2) use the count/sum in the findspec rather than querying once for each. Certainly looks much better.
11:22 < stub> Yup.
11:22 < noodles775> Or should I just use the query verbatim (so we know exactly what's being executed)?
11:22 < noodles775> (and thanks!)
11:22 < stub> Using Storm to generate the query should give you pretty much the same thing
11:23 < stub> You can check by turning on the storm SQL tracing. Or getting a user requested oops report.
11:23 -!- zyga [~zyga@ubuntu/member/zyga] has quit [Ping timeout: 252 seconds]
11:24 < stub> I've been looking into indexes - BuildFarmJob.status and Archive.require_virtualized help a little with the existing query, but not much and not at all with the count/sum query
}}}