Ok, I understand your use case, it seems that my trick with shared result will not help here.
Then lets dive a bit deeper into your use case: What is your main concern? Throughput, response time, fault tolerance, too large data volume for a single server, etc...? I mean you've made some decisions in your setup (like choosing 2 nodes with partitioned cache and 0 backups) and I want to understand if your setup matches your use case at all. May be it makes sense to switch to replicated cache or something? Sergi 2015-08-27 21:48 GMT+03:00 javadevmtl <[email protected]>: > So 2 different web requests will > put new objects in and then run the same queries, but each web request > needs > to have it's own responses back. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Re-Query-performance-tp1009p1161.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
