[ https://issues.jboss.org/browse/ISPN-6706?page=com.atlassian.jira.plugin.... ] William Burns edited comment on ISPN-6706 at 5/25/16 9:42 AM: -------------------------------------------------------------- If you are running a cluster I just noticed we don't have a very simple optimization of only running purge on the coordinator node when a shared store is used. This means that without this all nodes may be hitting the DB server at approximately the same time, which is probably why it is killing your DB response times. Another thing I would suggest is to limit how often the cache writer purge is performed in comparison to in memory (it could be ran every 5th memory purge for example). And looking closer at the JPAStore and Jdbc*Store implementations they should be using a simple select that only returns expired entries. I am not sure if we have indexes on these fields or not though, I haven't looked too closely at these classes (which may be causing a full table scan). Also the optimization you have right now could still be used but we would have to limit it as the following: # Only supported with 1 cache loader/writer (note we can have multiple configured) # Store state in the persistence manager to guarantee evict was never called was (Author: william.burns): If you are running a cluster I just noticed we don't have a very simple optimization of only running purge on the coordinator node when a shared store is used. This means that without this all nodes may be hitting the DB server at approximately the same time, which is probably why it is killing your DB response times. Another thing I would suggest is to limit how often the cache writer purge is performed in comparison to in memory (it could be ran every 5th memory purge for example). And looking closer at the JPAStore and Jdbc*Store implementations they should be using a simple select that only returns expired entries. I am not sure if we have indexes on these fields or not though, I haven't looked too closely at these classes (which may be causing your full table scan). Also the optimization you have right now could still be used but we would have to limit it as the following: # Only supported with 1 cache loader/writer (note we can have multiple configured) # Store state in the persistence manager to guarantee evict was never called -- This message was sent by Atlassian JIRA (v6.4.11#64026)