Hi Kevin,

This is the number of keys involved into PUT or GET operation. If there is
1 key, then *IgniteCache.get() *or *IgniteCache.put() *operation was used.
If there are more keys, then we benchmarked *IgniteCache.getAll() *or
*IgniteCache.putAll()
*operations.

On Thu, Aug 4, 2016 at 11:08 AM, Zhengqingzheng <zhengqingzh...@huawei.com>
wrote:

> Hi  there,
>
> I am reading ignite benchmark test result from this address:
> http://www.gridgain.com/resources/benchmarks/ignite-vs-hazelcast-benchmarks
>
> And I see there are some graph result labeled with descriptions like this:
> Graphs: 1 key
> <http://www.gridgain.com/wp-content/benchmarks/ignite-vs-hazelcast/tx-put/006-1.5.0.final-646926c3-tx-optimistic-put-1-backup/Results.html>
> , 2 keys
> <http://www.gridgain.com/wp-content/benchmarks/ignite-vs-hazelcast/tx-put/014-1.5.0.final-646926c3-tx-putAll-bs2-1-backup/Results.html>
> , 6 keys
> <http://www.gridgain.com/wp-content/benchmarks/ignite-vs-hazelcast/tx-put/015-1.5.0.final-646926c3-tx-putAll-bs-6-1-backup/Results.html>
> , 10 keys
> <http://www.gridgain.com/wp-content/benchmarks/ignite-vs-hazelcast/tx-put/016-1.5.0.final-646926c3-tx-putAll-bs-10-1-backup/Results.html>
> .
>
> Can anyone gives me a rough description for the meaning of different keys
> in the test?
>
>
>
>
>
> Best regards,
>
> Kevin
>
>
>
>
>

Reply via email to