You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "Akash R Nilugal (Jira)" <ji...@apache.org> on 2020/08/18 09:09:00 UTC
[jira] [Resolved] (CARBONDATA-3919) Improve concurrent query
performance
[ https://issues.apache.org/jira/browse/CARBONDATA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akash R Nilugal resolved CARBONDATA-3919.
-----------------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
> Improve concurrent query performance
> ------------------------------------
>
> Key: CARBONDATA-3919
> URL: https://issues.apache.org/jira/browse/CARBONDATA-3919
> Project: CarbonData
> Issue Type: Improvement
> Reporter: Ajantha Bhat
> Assignee: Ajantha Bhat
> Priority: Major
> Fix For: 2.1.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> problem1: when 500 queries executed concurrently.
> checkIfRefreshIsNeeded method was synchronized. so only one thread was working at time.
> But actually synchronization is required only when schema modified to drop tables. Not for whole function
>
> solution: synchronize only remove table part. Observed 500 query total performance improved from 10s to 3 seconds in cluster.
>
> problem2:
> TokenCache.obtainTokensForNamenodes was causing a performance bottleneck for concurrent queries. so, removed it
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)