[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-5452: --------------------------------------- Hi Prashant, there are two aspects at play: latency (response time) for a single query, and how many queries you can get done per unit of time (often measures as queries / second). The response time of a single query is expected to be longer for a remote query (of course! since it goes over your network) but the execution strategy is identical among all three approaches. The amount of queries per second handled by a single server is approximately the same for each of the three as well: Remote Query adds a little overhead toll as it's processing remote calls, but that being only a minor aspect it should only provide a small deviation. In other words, even though the latency would be higher, I don't expect significant changes in the amount of queries throughput the system can handle. RMI is not as efficient as Hot Rod so that makes your tests even more surprising. I can't comment on the 50-100 us: that seems a reasonable figure but it highly depends on the index size, the kind of queries, the kind of hardware and general OS tuning. What is important to take away is that wathever figure you can get on remote query, you should be able to better that when using embedded query. {quote}... then we are sure its an application issue{quote} Don't forget it might be a problem of tests design. I wouldn't be surprised if some of your clients get in locking problems because of "too good" performance from the server. Similarly you could have some race in data collection on the testing clients. -- This message was sent by Atlassian JIRA (v6.3.15#6346)