Re: 回复：Re: 答复: Cache.invoke are terribly slow and can't update cache

[vkulichenko <va...@gmail.com>]

Shawn,

You just should keep in mind that this is an object that will be serialized,
sent across network and invoked on other side. The purpose of entry
processor is to be executed on server side and atomically read and update a
single entry. Having said that, the logic you described doesn't make much
sense there.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-invoke-are-terribly-slow-and-can-t-update-cache-tp9676p9712.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

答复: 回复：Re: 答复: Cache.invoke are terribly slow and can't update cache

[Shawn Du <sh...@neulion.com.cn>]

Thanks Val, that's good.

-----邮件原件-----
发件人: vkulichenko [mailto:valentin.kulichenko@gmail.com] 
发送时间: 2016年12月23日 9:47
收件人: user@ignite.apache.org
主题: Re: 回复：Re: 答复: Cache.invoke are terribly slow and can't update
cache

Shawn,

You just should keep in mind that this is an object that will be serialized,
sent across network and invoked on other side. The purpose of entry
processor is to be executed on server side and atomically read and update a
single entry. Having said that, the logic you described doesn't make much
sense there.

-Val



--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-invoke-are-terribly-slo
w-and-can-t-update-cache-tp9676p9712.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.