ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yakov Zhdanov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-3233) need to optimize injections
Date Thu, 02 Jun 2016 05:25:59 GMT
Yakov Zhdanov created IGNITE-3233:

             Summary: need to optimize injections
                 Key: IGNITE-3233
                 URL: https://issues.apache.org/jira/browse/IGNITE-3233
             Project: Ignite
          Issue Type: Improvement
            Reporter: Yakov Zhdanov
            Assignee: Semen Boikov
            Priority: Blocker
             Fix For: 1.7

I want to check how this closure performs vs empty one:

ignite.compute().affinityCall(xx, xx, new IgniteCallable<Object>() {
    Ignite ignite;
    ApplicationContext ctx;
    Object bean1;
    Object bean2;
    @Override public Object call() throws Exception {
        bean1 = ctx.getBean(bean1class);
        bean2 = ctx.getBean(bean2class);
        return null;

Closure above is 3 times slower than Noop closure. Injections should be optimized.

I see the following options:
# Annotations
## Introduce SpringAware annotation and annotate each object that will need injection including
SPI and internal stuff
## Support Spring Autowire annotation.
## I am not sure about the approach. We can use ApplicationContext.autowire() or generate
and compile code that will do injections.
# Interfaces
## IgniteAware
## Spring ApplicationContext aware
## ...

Implementor should suggest and back solution with microbenchmarks.

This message was sent by Atlassian JIRA

View raw message