[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-5452: --------------------------------------- I've been looking at the method invocations, and agree with you that {{HSQueryImpl.buildSearcher(}} seems to be a significant difference. But exploring further, they both invoke ultimately the method {{CRC32.updateBytes(int, byte[], int, int)}}, which is the slow point. In the Infinispan Query case this consumes 7.39%, in the RMI based example this consumes 2.02%. Your profiling results are sampling, so it's possible that one case seems higher *relatively* as it's being invoked more (looks like we agree on the conclusion so far?). But what I'm reading out of this, is not that Infinispan Query decides to not reuse the IndexReader but instead decides to reopen it, what I'm reading is that the Infinispan Query scenario is running many more queries. Could you confirm this by running a profiler section - or just logging - to count how many queries one case is doing vs how many queries the other is doing? I can't read that from sampling output, but in case I think there's a problem with your benchmark, maybe because the Infinispan Query case is faster you're getting many more queries done on it and that would explain the higher rate of index reader reopening events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)