Internal thread-pool specifics

[Arindam Mukherjee]

When is the internal thread-pool used by futures spawned?
Is this a dynamic pool or do the threads remain running for the rest of the process' lifetime?

Arindam

[Jerry D'Antonio]

The global thread pool is dynamic. It is configured to begin with 0 threads and grow as necessary. During periods of inactivity it will release unused threads. The pool itself is lazy initialized. The first time a job is post to the pool (via Future, Promise, Actor, etc.) the pool will be created and the first thread will be started. After that the pool will manage itself for the lifetime of the application.

Best regards,
Jerry

--
You received this message because you are subscribed to the Google Groups "Concurrent Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concurrent-ru...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.