Delete is a fairly expensive operation, but I think the spikes are probably from require statements.  Currently there doesn't seem to be a way around this, as in-lining all the code also makes the CPU spike. The only solace is that when using `module.exports.loop` your require statements aren't always run.