Reining in runaway reports
Like Del Shannon, I've got a little runaway. But for me, it's a runaway report, one of the supplied ones (see Running report pyElapsedStatusTrend causing memory issues?)
I'm wondering if we can produce a list, for each report, focusing on whether it could potentially consume too much time/CPU.
- Is paging not used?
- What is the max rows?
- What source tables is this coming from?
- What are the number of records in the source table?
- How long does a count(*) using the standard
- What calls this (other rule, or user directly), and how are parameters supplied?