Re: Cache.replace-K-V-V- performing slow

[Andrei Aleksandrov]

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 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 <tarun.swprofessio...@gmail.com 
<mailto:tarun.swprofessio...@gmail.com>>:

    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) Ignite api call.
    Out of 77.9 by replace, 39% is taken by GridCacheAdapater.equalVal
    and 38.5%
    by GridCacheAdapter.put

    Attaching the profiling snapshot ,Can someone please check and
    suggest what
    could be the cause or some known issue with this version ?
    <http://apache-ignite-users.70518.x6.nabble.com/file/t2364/cache.jpg>

    Let me know for any further query need to answer this please.

    Regards,
    Tarun



    --
    Sent from: http://apache-ignite-users.70518.x6.nabble.com/