groundhog is great for iterating on a single invocation, but for production use the same task may be running 1000s of times. We want to make sure the very slight overhead doesn't scale poorly in the worst case, and if it does we can diagnose / rethink the bottlenecks
groundhog is great for iterating on a single invocation, but for production use the same task may be running 1000s of times. We want to make sure the very slight overhead doesn't scale poorly in the worst case, and if it does we can diagnose / rethink the bottlenecks