Ignite’s strength is an ability to store and process data in a distributed way in-memory. It means that while Ignite might loose to an RDBMS in a single machine comparison scenario, it will outperform in the scenarios where a lot of data is stored cluster wide.
Considering this, try to start a cluster of separated machine, preload data that’s meaningful to your application/service and execute benchmarks for some period of time (minutes, hours). The whole point is that it should be just a single execution of a query on a single machine. Hope it helps. Denis > On Dec 12, 2017, at 12:34 PM, bagsiur <[email protected]> wrote: > > Thanks for reply. > > What do you mean with "warmed up" the JVM prior testing? > > How can I do this? > > Do you mean to prepare JAVA application with some SQL queries like my PHP > scripts from first post, and run it in JVM to check query time? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
