[jira] [Updated] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated PHOENIX-4398: Attachment: PHOENIX-4398_V1.patch Recommit PHOENIX-4398.patch as PHOENIX-4398_V1.patch. See what will happen. > 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, PHOENIX-4398_V1.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)
[jira] [Comment Edited] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281553#comment-16281553 ] Albert Lee edited comment on PHOENIX-4398 at 12/7/17 9:30 AM: -- ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureIT ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexReplicationIT This two UnitTests can pass in my evniroment. Is QA have something wrong at that time? was (Author: albertlee...@gmail.com): ./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)
[jira] [Commented] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Updated] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated PHOENIX-4398: Description: 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. was: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. > 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)
[jira] [Updated] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated PHOENIX-4398: Attachment: PHOENIX-4398.patch > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated PHOENIX-4398: Attachment: (was: PHOENIX-4398_v1.patch) > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated PHOENIX-4398: Attachment: PHOENIX-4398_v1.patch > 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_v1.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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated PHOENIX-4398: Attachment: (was: PHOENIX-4398_v1.patch) > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PHOENIX-4398) Change QueryCompiler get column expressions process from serial to parallel.
[ https://issues.apache.org/jira/browse/PHOENIX-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated PHOENIX-4398: Attachment: PHOENIX-4398_v1.patch > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
