mapreduce nif terminator loop is using CPU time _of all process' threads_ as a clock causing 5 seconds to elapse _much_ earlier than wall clock 5 seconds under load

clock(3) is using process CPU time. Which is kinda nice except that it'll be sum of CPU times of all threads. If we have 8-16 or more cores that time will advance 8-16 or more times faster than wall clock time. Thus termination timeout will occur much earlier than 5 seconds. Seemingly.