You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Igor Sapego (JIRA)" <ji...@apache.org> on 2017/04/28 13:12:04 UTC
[jira] [Created] (IGNITE-5111) Refactor Platform remote job
execution routine for PlatformClosureJob
Igor Sapego created IGNITE-5111:
-----------------------------------
Summary: Refactor Platform remote job execution routine for PlatformClosureJob
Key: IGNITE-5111
URL: https://issues.apache.org/jira/browse/IGNITE-5111
Project: Ignite
Issue Type: Task
Components: platforms
Affects Versions: 1.9
Reporter: Igor Sapego
Fix For: 2.1
If we take a look at {{org.apache.ignite.internal.processors.platform.compute.PlatformClosureJob}}
We can see code as follows:
{code}
createJob(ctx);
try (PlatformMemory mem = ctx.memory().allocate()) {
//...
ctx.gateway().computeJobExecute(mem.pointer());
//...
}
finally {
ctx.gateway().computeJobDestroy(ptr);
}
{code}
It also seems like {{ptr}} is not used anywhere, so it looks like this can be replaced with single call to native code instead of three. We also can get rid of the handle allocation for the closure object in platform code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)