phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
Date Thu, 07 Dec 2017 09:30:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281553#comment-16281553
] 

Albert Lee commented on PHOENIX-4398:
-------------------------------------

./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexReplicationIT

> Change QueryCompiler get column expressions process from serial to parallel.
> ----------------------------------------------------------------------------
>
>                 Key: PHOENIX-4398
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4398
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.11.0, 4.13.0
>            Reporter: Albert Lee
>             Fix For: 4.11.0, 4.13.0
>
>         Attachments: PHOENIX-4398.patch
>
>
> When QueryCompiler compile a select sql, the process of getting column expressions is
a serial process. The performance is ok when the table is narrow. But when compile a wide
table(e.g. 130 columns in my use case), The time-consuming of this step is very high, over
70ms. So I change TupleProjector(PTable projectedTable) from serial for loop to parallel future.
> Because this is just modify code performance, not add new feture, so there is no unit
test.



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

Mime
View raw message