EDIT: I noticed that the analysis alone does not detect large spikes in cpuTime so I changed the quota exceeded expression to include a hard limit on the cpuTime. Together the system is able allow chip cpuTime spikes to exceed the quota limit based on how much much their cpuTime is varying (with more variance allowing the spike to exceed the quota limit more) and is able to catch big spikes with a hard cpuTime limit.
EDIT: I noticed that the analysis alone does not detect large spikes in cpuTime so I changed the quota exceeded expression to include a hard limit on the cpuTime. Together the system is able allow chip cpuTime spikes to exceed the quota limit based on how much much their cpuTime is varying (with more variance allowing the spike to exceed the quota limit more) and is able to catch big spikes with a hard cpuTime limit.