yakov wrote > What are your timings now? on two local nodes, after jvm is warmed up (~100 executions), it's running in average 30ms instead of 6 sec when result is returned in return/reduce phase. This is a huge improvement! I can take it now as a basis and start adding some additional behavior on top of it (task status persistence, custom job exception handling etc.).
Just for my understanding - after reading the javadoc, I've understood that this annotation is exactly for use-cases where results of distributed jobs are not required to be returned to a caller/reducet although these jobs still can write/read from distributed cache in collocate manner (when https://issues.apache.org/jira/browse/IGNITE-5037 is implemented), right? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/