Alexey Kukushkin created IGNITE-25769:
-----------------------------------------
Summary: ComputeTaskContinuousMapper in Ignite.NET
Key: IGNITE-25769
URL: https://issues.apache.org/jira/browse/IGNITE-25769
Project: Ignite
Issue Type: Improvement
Components: .NET
Affects Versions: 2.17
Reporter: Alexey Kukushkin
Assignee: Alexey Kukushkin
We are missing {{ComputeTaskContinuousMapper}} in Ignite.NET, which is
available in the Ignite Java API but not in .NET. The official Ignite
documentation only briefly mentions {{ComputeTaskContinuousMapper}} in the
[Pre-defined
Resources|https://ignite.apache.org/docs/latest/resources-injection#pre-defined-resources]
section. Based on our practical experience, we have identified additional
requirements that could be addressed by this feature:
* Enable development of distributed computations in .NET without requiring an
upfront definition of all compute jobs on the "mapping" node.
* Optimize memory usage: our application occasionally creates over one hundred
thousand compute jobs, each with a significant memory footprint. This might
lead to the "mapping" node going out of memory.
* Facilitate better job management and fine-tuning. Continuous job creation
enables optimization of job parameters based on the current runtime.
In summary, these requirements necessitate *streaming* of compute jobs.
Exposing the existing Java API's {{ComputeTaskContinuousMapper}} functionality
in .NET would satisfy these needs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
