Hello Ignite team, As we are evaluating potential usage of Ignite for our Analytics projects, I would like to ask the following:
- *Compute Grid*: what is in practical difference between Distributed Closures and Executor Service? For example if I have computations that I want to distribute (multiple callables) and I want to take advantage of all cores of the cluster (based on the existing load of course) so I get *fast results*, is there a difference between using exec.submit() VS ignite.compute().call()? Moreover, if some distributed calculation is in progress and occupies all the cores of the cluster and in the meantime a new distributed calculation is requested, then what will happen? Is there some queue mechanism and how is it configured? Which is the best way to implement this? Is there need for a messaging queue or we could rely to thread pool sizes configurations etc. ? - If I want to pass data to callables, for example Lists of objects, small to -medium size (collections from 2000 to 6000 objects maximum, with average object size some ~200KBs) what is the best way to do this: to pass them as argument in callables or put them in the distributed cache for the callables to pick them up from there? Thank you. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
