[jira] [Resolved] (CARBONDATA-1436) optimize concurrency control for datamap

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (CARBONDATA-1436) optimize concurrency control for datamap

Akash R Nilugal (Jira)

     [ https://issues.apache.org/jira/browse/CARBONDATA-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacky Li resolved CARBONDATA-1436.
----------------------------------

> optimize concurrency control for datamap
> ----------------------------------------
>
>                 Key: CARBONDATA-1436
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-1436
>             Project: CarbonData
>          Issue Type: Improvement
>          Components: core
>            Reporter: xuchuanyin
>            Assignee: xuchuanyin
>            Priority: Minor
>             Fix For: 1.2.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> # Scenario
> `DataMapStoreManager` provides a synchronized interface `getDataMap` to retrieve a table's `TableDataMap`. It will cause performance problems in current query scenario when all the queries have to wait the former query finished.
> # Analyze
> We can make the concurrent control in table scope instead of global scope.
> # Modification
> + Synchronized by table.
> + Use double checked locking to reduce lock overhead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)