I'm sure this has been discussed before but having watched hundreds of
thousands of cpuhrs being wasted by difficult-to-detect hung jobs, I'd
be keen to know why there isn't some sort of "spin-wait backoff" option.
For example, a way to specify spin-wait for x seconds/cycles/iterations
then backoff to lighter and lighter cpu usage.  At least that way, hung
jobs would become self-evident.

Maybe there is already some way of doing this?

Thanks,
David

Reply via email to