[ https://issues.jboss.org/browse/ISPN-9722?page=com.atlassian.jira.plugin.... ] Will Burns commented on ISPN-9722: ---------------------------------- {quote} Will Burns personally I'm a bit skeptical about using a separate thread pool: with the default CallerRunsPolicy we're always going to run some tasks in the caller thread, so it adds a lot of edge cases. {quote} We shouldn't ever be hitting the CallerRunsPolicy. The thread pool should have a large amount of threads and a large queue. We don't ever want to run this on the soon to be very precious CPU threads. {quote} And I wonder if we should make an exception when the store is asynchronous: blocking to wait for space in the write-behind queue is the same as blocking to wait for a free worker thread (or space in the thread pool queue). {quote} Adding support for actual asynchronous stores is a different PR after this. All of ours are currently sync with the given SPI, this needs to be rectified later with a new SPI to enable it. Then the running on a different thread can be decided by the store instead, however we aren't there yet. We shouldn't be blocking to wait for space in the queue, if we are that is a big problem as that would mean we are blocking the CPU thread when we shouldn't be. -- This message was sent by Atlassian Jira (v7.12.1#712002)