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

[shawn.du]

Thanks Val!

Now I understood entryprocessor better. as to "error prone", I meant if we follow the document,

it will be error prone.  For EntryProcessor is just an interface, it doesn't prohibit user to use lamda or anonymous classes. 

When we implement the interface at client side, the user may use client side global variables/classes/instances(some of them even will start new threads), I don't know it will work or not, at least it will introduce much complexity. At yesterday's debuging, I event don't see much useful logs.  back to the document, I think it can be improved and give some recommendations. 

Thanks

Shawn  

在2016年12月23日 03:03， vkulichenko <valentin.kuliche...@gmail.com> 写道：

Shawn,

#1 - Yes, peer class loading is needed if you don't have entry processor
implementation class deployed on server nodes.
#2 - Correct. Moreover, I would recommend not to use lambdas or anonymous
classes for anything that can be serialized, but to use static classes
instead (this is actually a recommendation for Java in general, not only for
Ignite). This will give you much more control on what is serialized along
with entry processor and will simplify the understanding of how it is
executed.

Can you clarify why do you think it's error prone?

-Val



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