[ https://issues.jboss.org/browse/ISPN-4650?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-4650: --------------------------------------- {quote} I'd like to explore a 3rd alternative besides using auto switch and queues, which is relying on UpdateExtWorkDelegate. Some local tests demonstrated this kind of delegate to be closer performance wise to the AddWorkDelegate. I'm aware the implications of its usage (being recommended if keys are unique in an index), and I think infinispan ticks the boxes, doesn't it?{quote} It's not too uncommon for people to share a same index for different types. We would need to make sure that such configurations are not possible; maybe that's a clever logic which could be applied by the automatic configuration approach you've been working on? But if the user is allowed to change all the configuration options as he can do today, this is unfortunately not a safe assumption. An alternative could be to always perform both the ADD and the REMOVE operations, but allowing IndexWriter commits and IndexReader refreshes to skip the flush on the delete operations: when Query returns a List of matches, it's supposed going to ignore the matches which it won't load. This doesn't work when projections are being used (But we can know when they are been used) and might break some pagination operations: in Search (ORM) the pagination is compensated for by adding some entries from the next page, but the exact indexes of page boundaries might be inaccurate. -- This message was sent by Atlassian JIRA (v6.3.1#6329)