You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexandr Fedotov (JIRA)" <ji...@apache.org> on 2017/04/13 13:04:41 UTC

[jira] [Created] (IGNITE-4957) First join query execution in client mode takes too long when there are many caches on remote nodes

Alexandr Fedotov created IGNITE-4957:
----------------------------------------

             Summary: First join query execution in client mode takes too long when there are many caches on remote nodes
                 Key: IGNITE-4957
                 URL: https://issues.apache.org/jira/browse/IGNITE-4957
             Project: Ignite
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 1.9
            Reporter: Alexandr Fedotov
             Fix For: 2.1


When there are many caches deployed on server nodes and a query containing joins is executed on a client for the first time it takes much time to complete compared to the following executions.

If caches aren't enabled locally then the first query tries to load all the missing caches by calling
{{org.apache.ignite.internal.processors.cache.GridCacheProcessor#createMissingCaches}}
createMissingCaches internally sends a request per each registered but not enabled cache.
Performance could be improved by performing a batch request.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)