ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5111) Refactor Platform remote job execution routine for PlatformClosureJob
Date Mon, 10 Jul 2017 07:09:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov updated IGNITE-5111:
------------------------------------
    Fix Version/s:     (was: 2.1)
                   2.2

> 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
>            Priority: Minor
>             Fix For: 2.2
>
>
> 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.4.14#64029)

Mime
View raw message