When developing code, unit tests and interactive testing naturally tend to start with small numbers. As the number of objects increases, the execution time has to increase in proportion. Execution time flourishes as the square of the number of objects or the cube of the number of objects.
Limit forces bad algorithm to be replaced by a better one. However, the customer is stuck unable to work until it is fixed. There are two contexts that involve two different approaches. In more complicated cases, the approaches can be combined to fix the problem.