[
https://issues.apache.org/jira/browse/IMPALA-10682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer updated IMPALA-10682:
-------------------------------------
Description:
The following command takes 1.5 sec with hs2 and 8.5 sec with hs2-http ptotocol
on my dev machine:
{code}
shell/impala_shell.py -B -q "select * from tpch_parquet.lineitem limit 100000;"
--protocol hs2-http > /dev/null
{code}
Profiling has shown that the main culprit is calling socket.recv() 2809090
times. The root cause is the lack of buffering in our current http client
implementation.
was:
The following command takes 1.5 sec with hs2 and 8.5 sec with hs2-http ptotocol
on my dev machine:
{code}
shell/impala_shell.py -B -q "select * from tpch_parquet.lineitem limit 100000;"
--protocol hs2 > /dev/null
{code}
Profiling has shown that the main culprit is calling socket.recv() 2809090
times. The root cause is the lack of buffering in our current http client
implementation.
> impala-shell is slow with hs2-http
> ----------------------------------
>
> Key: IMPALA-10682
> URL: https://issues.apache.org/jira/browse/IMPALA-10682
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Reporter: Csaba Ringhofer
> Priority: Major
>
> The following command takes 1.5 sec with hs2 and 8.5 sec with hs2-http
> ptotocol on my dev machine:
> {code}
> shell/impala_shell.py -B -q "select * from tpch_parquet.lineitem limit
> 100000;" --protocol hs2-http > /dev/null
> {code}
> Profiling has shown that the main culprit is calling socket.recv() 2809090
> times. The root cause is the lack of buffering in our current http client
> implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
