You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/07/09 18:32:05 UTC
[jira] [Resolved] (PHOENIX-1073) A memory table in every region is
needed?
[ https://issues.apache.org/jira/browse/PHOENIX-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor resolved PHOENIX-1073.
-----------------------------------
Resolution: Invalid
> A memory table in every region is needed?
> -----------------------------------------
>
> Key: PHOENIX-1073
> URL: https://issues.apache.org/jira/browse/PHOENIX-1073
> Project: Phoenix
> Issue Type: Wish
> Reporter: jay wong
>
> When a do a group by query.
> We assume that a Region has 30M data.
> 100K row which include 30 kv per row
> And the RT of GroupedAggregateRegionObserver is about 3 sec.
> but most of time. in fact nearly 2.2 sec is spend on RegionScaner scan all the row.
> I have a test. first time scan all of the data into memory.
> the second time only load the data from memory.
> the RT of GroupedAggregateRegionObserver execute only 0.7s.
> So If a memory table is needed for Phoenix computational intensive scene
--
This message was sent by Atlassian JIRA
(v6.2#6252)