Hi,
I have also described the possible problem here -
https://stackoverflow.com/questions/59950157/why-apache-ignite-cache-replace-k-v-v-api-call-performing-slow
BR,
Andrei
1/31/2020 12:33 PM, Ilya Kasnacheev пишет:
Hello!
I'm not sure the benchmarking is relevant, since most of work
Hello!
I'm not sure the benchmarking is relevant, since most of work happens on
server nodes and you are not benchmarking their threads.
Are you sure you're not doing more replace()s than necessary?
Regards,
--
Ilya Kasnacheev
вт, 28 янв. 2020 г. в 15:27, tarunk :
> Hi All,
>
> We are
Hi All,
We are running Ignite cluster with 12 nodes running Ignite 2.7.0 on openjdk
1.8 RHEL platform.
We saw some slowness with one of our process and when we tried to drill it
further by profiling the JVM, the main culprit (taking ~78% of total time)
seems to be coming from cache.repalce(K,V,V)