I'd go for #A to limit cross-effects between oak and other layers. The reason one would want to use the default pool for #4 is probably the idea that you'd want to avoid "wasting" a thread in the oak-thread-pool and rather rely on a shared one. But arguably, that should be an optimization of the thread pool provider itself: that provider could be more intelligent and allocate threads from an under-used pool elsewhere - if that were more performant.
But from a logical point of view, I'd argue it's better to have an oak-dedicated thread-pool. Cheers, Stefan On 19/07/16 10:06, "Chetan Mehrotra" <[email protected]> wrote: >On Tue, Jul 19, 2016 at 1:21 PM, Michael Dürig <[email protected]> wrote: >> Not sure as I'm confused by your description of that option. I don't >> understand which of 1, 2, 3 and 4 would run in the "default pool" and >>which >> should run in its own dedicated pool. > >#1, #2 and #3 would run in dedicated pool and each using same pool. >Pool name would be 'oak'. Also see OAK-4563 for the patch > >While for #4 default pool would be used as those are non blocking and >short tasks > >Chetan Mehrotra
