Sam, >> Why does invoking remote method is taking 50% of time? Is it because of concurrency and entry processor will execute under a lock internally? >> Could you please share a small reproducer project.
>> Is there any better way to deal with this usecase? Have you tested with only heap memory? Thanks, Pavel 2018-04-06 2:39 GMT+07:00 javastuff....@gmail.com <javastuff....@gmail.com>: > Thanks Pavel for reply. > > /"When you store entries into the off-heap, any update operation requires > copying value from the off-heap to the heap." / > I am updating using remote entry processor, does that also need to copy > value to calling heap? If yes then no benefit using entry processor here, I > can fetch and put, probably with a lock. > > Why does invoking remote method is taking 50% of time? Is it because of > concurrency and entry processor will execute under a lock internally? > > Coping existing and incoming bytes, must be generating a lot for GC. > > Is there any better way to deal with this usecase? right now it seems > slower > than DB updates. > > Thanks, > -Sam > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Regards Pavel Vinokurov
