On Thu, Sep 7, 2017 at 8:52 AM, Yakov Zhdanov <[email protected]> wrote:
> Guys, according to this - > http://apache-ignite-users.70518.x6.nabble.com/Task-manageme > nt-MapReduce-amp-ForkJoin-performance-penalty-td16542.html > - I would think that we need to disable result caching by default.0 > Or at least find out why it is so costly. > Yakov, I was not aware that we have compute job result caching. Can you please describe what is being cached?
