You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/06/21 13:47:00 UTC
[jira] [Updated] (IGNITE-5382) SQL: frequent switch between schemas
cause severe slowdown
[ https://issues.apache.org/jira/browse/IGNITE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-5382:
------------------------------------
Fix Version/s: 2.1
> SQL: frequent switch between schemas cause severe slowdown
> ----------------------------------------------------------
>
> Key: IGNITE-5382
> URL: https://issues.apache.org/jira/browse/IGNITE-5382
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
> Reporter: Vladimir Ozerov
> Assignee: Sergey Kalashnikov
> Labels: important, performance
> Fix For: 2.1
>
>
> We have thread-bound cached connection to H2 database which is bound to specific schema. See {{IgniteH2Indexing.connectionForThread}}.
> When query with different schema is executed, we call {{SET SCHEMA}} command, which is rather expensive and may cause slowdown when queries form different caches are executed.
> To avoid this we should maintain thread-local map of such connections. Be careful with concurrency and resource leaks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)