Chris,
After looking at your code, the only slow down that may have occurred
between 1.9 and 2.0 is the actual cache "get(...)" operation. As you may
already know, Ignite 2.0 has moved data off-heap completely, so we do not
cache data in the deserialized form any more, by default. However, you can
Absolutely agree here. I think if we can add getAll() benchmark and run it
with batch sizes of 5 and 10.
Thanks!
--
Yakov Zhdanov, Director R&D
*GridGain Systems*
www.gridgain.com
2017-05-12 10:48 GMT+03:00 Sergi Vladykin :
> According to our benchmarks Ignite 2.0 is not slower for get operation
According to our benchmarks Ignite 2.0 is not slower for get operation. I
think we need some minimal reproducer that shows the performance
degradation before making any conclusions.
Sergi
2017-05-12 1:10 GMT+03:00 Yakov Zhdanov :
> Cross-posting to devlist.
>
> --Yakov
>
Cross-posting to devlist.
--Yakov
