[
https://issues.jboss.org/browse/ISPN-9722?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-9722:
------------------------------------
[~william.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.
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).
Perform all CacheStore operations on a separate thread
------------------------------------------------------
Key: ISPN-9722
URL:
https://issues.jboss.org/browse/ISPN-9722
Project: Infinispan
Issue Type: Enhancement
Components: Loaders and Stores
Reporter: Will Burns
Assignee: Will Burns
Priority: Major
Fix For: 10.0.0.Final
Persistence is one of the few remaining systems that are not non blocking. This needs to
be remedied. We will eventually need to add an SPI that does this, but for now we need to
offload the persistence operations to a different thread pool.
This should only require changes in the PersistenceManager to return non blocking methods
(ie. return CompletionStage). We should then update references to use non blocking when
possible.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)