>> I'm not sure what this test doing The test is demonstrating significant reduction of the throughput when empty QueryEntity added to the cache config.
>> how many ops are done per iteration? Iterations are time based. It uses the default defined by JMH. One iteration conducted to warm up during 5 seconds and three iterations conducted to take the measurement using default interval (I think something around 10 seconds). >> Why do you need to start Ignite for every iteration No particular reason. Done just in sake of clean benchmark results. What difference does it make? >> but I want to say that adding indexing to your cache means having a >> primary key, in your case a composite primary key, and updating this >> index is going to take some CPU time, especially since there's nothing >> else to consume it. First of all, there are no explicit indexes defined by the test. The throughput got reduced from 51566.775 ops/s in simple K-V case to 22305.457 ops/s when "empty" QueryEntity added. It's more than 50%! Do you believe that implicit primary key creation has such severe impact? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
