[
https://issues.apache.org/jira/browse/PHOENIX-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369979#comment-14369979
]
Lars Hofhansl commented on PHOENIX-1752:
----------------------------------------
[~mujtabachohan], any chance to run your test magic?
The tricky part here is: Of course it'll be slower with the patch, since we're
limiting the number of threads to how many we said we'd use. As we add more
threads to the thread pool it should approach the old performance.
> Phoenix should not "early-start" TableResultIterators
> -----------------------------------------------------
>
> Key: PHOENIX-1752
> URL: https://issues.apache.org/jira/browse/PHOENIX-1752
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: 1752.txt
>
>
> Currently Phoenix early-starts TableResultIterators.
> I do not think that is correct; what happens is that the scanner will start
> working simply by being created, and the work is not handled by the
> threadpool. In other words merely creating the iterator will start to do
> work, regardless of how large the Phoenix pool is size. It might seem to be
> faster, but only because we're throwing more threads at it than we say we
> would. Making the threadpool larger should get us back to the same the
> performance.
> The main task here is to perf test this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
