[ https://issues.apache.org/jira/browse/IGNITE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandr Fedotov updated IGNITE-4957: ------------------------------------- Attachment: first_run_from_client.png First join query run on a client > 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 > Labels: performance > Fix For: 2.1 > > Attachments: first_run_from_client.png > > > When there are many caches deployed on server nodes and a query containing > joins is executed on a client for the first time then 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)