It's an historic choice that once may be lifted. The limit is only there on the threadpool implementation.
An explanation is given on the website, stating the following:
The limitation of 60 concurrent threads only applies to the thread
pool. Thread pool is designed for fast execution of many small
requests, not as a storage for rarely-active threads.
You can just skip thread pool and use OTL tasks directly. That way you
can create many hundreds of them.
The reason for this limit is that deep inside [OtlTaskControl]TOmniTaskExecutor.WaitForEvent
uses MsgWaitForMultipleObjectsEx which has this limitation. If a real need occurs for task pools with more than 60 concurrently running threads, this limitation could be circumvented.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…