You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@impala.apache.org by 吴朱华 <ik...@gmail.com> on 2017/04/07 04:16:58 UTC
Re: Need to upgrade my one year old build for potential join perf improvement?
Hi guys:
Is there any change on metadata loading? The metadata loading used to 10sec.
2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
> thx^_^
>
> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>
>> If your build does not have runtime filters (which are a little more than
>> a year old), then the answer is yes: you should upgrade.
>>
>> Performance in general has been improving steadily over the last year.
>>
>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>
>>> The question is there any big join perf related improvement has
>>> implemented? Thx
>>>
>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>
>>> > Hi guys:
>>> >
>>> > I am currently using my one year old build (I guess 2016.3 CDH5-Trunk),
>>> > now I am facing a lot of join query situation(two big table joins), do
>>> I
>>> > need to upgrade my one year old build for potential join perf
>>> improvement?
>>> > Thx at advance^_^
>>> >
>>>
>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by 吴朱华 <ik...@gmail.com>.
@Antoni Ivanov
The cluster is new one, its size is small^_^
2017-04-11 0:02 GMT+08:00 Silvius Rus <sr...@cloudera.com>:
> On Sun, Apr 9, 2017 at 10:46 PM, Antoni Ivanov <ai...@vmware.com> wrote:
>
>> @Silvus How would this issue explain High cpu usage. It states the
>> threads are in state “waiting” in the bug.
>>
>
> The message I responded to stated 100% to 200% Catalog CPU usage, which
> means 1 to 2 cores fully used, which translates to 1 to 2 threads actually
> loading (and the other 15 or 14 possibly waiting on the same tables).
> That's behavior consistent with IMPALA-4765.
>
> There could be other reasons for this behavior. I'm not saying
> IMPALA-4765 is the root cause in this case, just that the described
> behavior matches the known issue.
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by Silvius Rus <sr...@cloudera.com>.
On Sun, Apr 9, 2017 at 10:46 PM, Antoni Ivanov <ai...@vmware.com> wrote:
> @Silvus How would this issue explain High cpu usage. It states the threads
> are in state “waiting” in the bug.
>
The message I responded to stated 100% to 200% Catalog CPU usage, which
means 1 to 2 cores fully used, which translates to 1 to 2 threads actually
loading (and the other 15 or 14 possibly waiting on the same tables).
That's behavior consistent with IMPALA-4765.
There could be other reasons for this behavior. I'm not saying IMPALA-4765
is the root cause in this case, just that the described behavior matches
the known issue.
Re: Need to upgrade my one year old build for potential join perf
improvement?
Posted by Antoni Ivanov <ai...@vmware.com>.
Hi,
@Silvus How would this issue explain High cpu usage. It states the threads are in state “waiting” in the bug.
Also I’ve noticed that High Cpu Usage can happen in our environment. When I did stack trace and saw the JVM threads are stuck in GC cycle.
We have a low memory for each impalad node (e.g 20G memory and the catalog size a bit over 2G ) so I’ve been thinking it’s possible that frequent GC cycle are causing
I am noticing memory of the range of 16GB for JVM (from impalas-node:25000/memz page)
@ikewu93 how much memory is allocated for Impala? How big is the catalog size (you can see it from statestored-node::25010/topics - catalog-update size(values))
(issue that could be causing big catalog size I think it is having a lot of (small) files or having a lot of partitions or having a lot of tables)
On Apr 10, 2017, at 1:36 AM, Silvius Rus <sr...@cloudera.com>> wrote:
One known issue that matches this condition was fixed on master, https://issues.apache.org/jira/browse/IMPALA-4765<https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_IMPALA-2D4765&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=8j7tFznmoySfY9RiEAZHgvi3kzcbJ_Zy6Hp9HYX4dDE&m=7b_obe2IcbquUHdyc1Dk-rjaodh9PdPOjsoJReq-S0c&s=TYmbZbxKkaoRiu2LTGlj9Kq8uRwSgkGfSKLkz7gikgg&e=>. It is not yet part of a release. The fix doesn't speed up the loading of the largest table, but it makes it more likely that loading of smaller tables can progress in parallel.
On Sun, Apr 9, 2017 at 12:30 AM, 吴朱华 <ik...@gmail.com>> wrote:
The issue will occur when the new table has been created or impalad has been just restarted.
2017-04-09 15:28 GMT+08:00 吴朱华 <ik...@gmail.com>>:
During 10-15sec loading, from top, we only can see 2-3sec more than 100%-200% java usage, other than that there is nothing serious working, and we will attach profile once we have it, and this question has been haunted us for year.
2017-04-09 15:13 GMT+08:00 吴朱华 <ik...@gmail.com>>:
Plus the schema we using is simple
2017-04-09 15:11 GMT+08:00 吴朱华 <ik...@gmail.com>>:
The current version using early 2016, the metadata loading is 10-15sec.
We haven't try the latest version, we hope the issue has been solved^_^
2017-04-07 14:08 GMT+08:00 Alex Behm <al...@cloudera.com>>:
What was your Impala version before and what is it now?
How fast was it before and how fast is it now?
On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com>> wrote:
Hi guys:
Is there any change on metadata loading? The metadata loading used to 10sec.
2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>>:
thx^_^
2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>>:
If your build does not have runtime filters (which are a little more than a year old), then the answer is yes: you should upgrade.
Performance in general has been improving steadily over the last year.
On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com>> wrote:
The question is there any big join perf related improvement has
implemented? Thx
2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>>:
> Hi guys:
>
> I am currently using my one year old build (I guess 2016.3 CDH5-Trunk),
> now I am facing a lot of join query situation(two big table joins), do I
> need to upgrade my one year old build for potential join perf improvement?
> Thx at advance^_^
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by 吴朱华 <ik...@gmail.com>.
cool
2017-04-10 6:36 GMT+08:00 Silvius Rus <sr...@cloudera.com>:
> One known issue that matches this condition was fixed on master,
> https://issues.apache.org/jira/browse/IMPALA-4765. It is not yet part of
> a release. The fix doesn't speed up the loading of the largest table, but
> it makes it more likely that loading of smaller tables can progress in
> parallel.
>
> On Sun, Apr 9, 2017 at 12:30 AM, 吴朱华 <ik...@gmail.com> wrote:
>
>> The issue will occur when the new table has been created or impalad has
>> been just restarted.
>>
>> 2017-04-09 15:28 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>
>>> During 10-15sec loading, from top, we only can see 2-3sec more than
>>> 100%-200% java usage, other than that there is nothing serious working,
>>> and we will attach profile once we have it, and this question has been
>>> haunted us for year.
>>>
>>> 2017-04-09 15:13 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>
>>>> Plus the schema we using is simple
>>>>
>>>> 2017-04-09 15:11 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>
>>>>> The current version using early 2016, the metadata loading is
>>>>> 10-15sec.
>>>>> We haven't try the latest version, we hope the issue has been
>>>>> solved^_^
>>>>>
>>>>> 2017-04-07 14:08 GMT+08:00 Alex Behm <al...@cloudera.com>:
>>>>>
>>>>>> What was your Impala version before and what is it now?
>>>>>>
>>>>>> How fast was it before and how fast is it now?
>>>>>>
>>>>>> On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi guys:
>>>>>>>
>>>>>>> Is there any change on metadata loading? The metadata loading used
>>>>>>> to 10sec.
>>>>>>>
>>>>>>> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>>>
>>>>>>>> thx^_^
>>>>>>>>
>>>>>>>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>>>>>>>
>>>>>>>>> If your build does not have runtime filters (which are a little
>>>>>>>>> more than a year old), then the answer is yes: you should upgrade.
>>>>>>>>>
>>>>>>>>> Performance in general has been improving steadily over the last
>>>>>>>>> year.
>>>>>>>>>
>>>>>>>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> The question is there any big join perf related improvement has
>>>>>>>>>> implemented? Thx
>>>>>>>>>>
>>>>>>>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>> > Hi guys:
>>>>>>>>>> >
>>>>>>>>>> > I am currently using my one year old build (I guess 2016.3
>>>>>>>>>> CDH5-Trunk),
>>>>>>>>>> > now I am facing a lot of join query situation(two big table
>>>>>>>>>> joins), do I
>>>>>>>>>> > need to upgrade my one year old build for potential join perf
>>>>>>>>>> improvement?
>>>>>>>>>> > Thx at advance^_^
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by Silvius Rus <sr...@cloudera.com>.
One known issue that matches this condition was fixed on master,
https://issues.apache.org/jira/browse/IMPALA-4765. It is not yet part of a
release. The fix doesn't speed up the loading of the largest table, but it
makes it more likely that loading of smaller tables can progress in
parallel.
On Sun, Apr 9, 2017 at 12:30 AM, 吴朱华 <ik...@gmail.com> wrote:
> The issue will occur when the new table has been created or impalad has
> been just restarted.
>
> 2017-04-09 15:28 GMT+08:00 吴朱华 <ik...@gmail.com>:
>
>> During 10-15sec loading, from top, we only can see 2-3sec more than
>> 100%-200% java usage, other than that there is nothing serious working,
>> and we will attach profile once we have it, and this question has been
>> haunted us for year.
>>
>> 2017-04-09 15:13 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>
>>> Plus the schema we using is simple
>>>
>>> 2017-04-09 15:11 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>
>>>> The current version using early 2016, the metadata loading is
>>>> 10-15sec.
>>>> We haven't try the latest version, we hope the issue has been solved^_^
>>>>
>>>> 2017-04-07 14:08 GMT+08:00 Alex Behm <al...@cloudera.com>:
>>>>
>>>>> What was your Impala version before and what is it now?
>>>>>
>>>>> How fast was it before and how fast is it now?
>>>>>
>>>>> On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
>>>>>
>>>>>> Hi guys:
>>>>>>
>>>>>> Is there any change on metadata loading? The metadata loading used to
>>>>>> 10sec.
>>>>>>
>>>>>> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>>
>>>>>>> thx^_^
>>>>>>>
>>>>>>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>>>>>>
>>>>>>>> If your build does not have runtime filters (which are a little
>>>>>>>> more than a year old), then the answer is yes: you should upgrade.
>>>>>>>>
>>>>>>>> Performance in general has been improving steadily over the last
>>>>>>>> year.
>>>>>>>>
>>>>>>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> The question is there any big join perf related improvement has
>>>>>>>>> implemented? Thx
>>>>>>>>>
>>>>>>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>>>>>
>>>>>>>>> > Hi guys:
>>>>>>>>> >
>>>>>>>>> > I am currently using my one year old build (I guess 2016.3
>>>>>>>>> CDH5-Trunk),
>>>>>>>>> > now I am facing a lot of join query situation(two big table
>>>>>>>>> joins), do I
>>>>>>>>> > need to upgrade my one year old build for potential join perf
>>>>>>>>> improvement?
>>>>>>>>> > Thx at advance^_^
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by 吴朱华 <ik...@gmail.com>.
The issue will occur when the new table has been created or impalad has
been just restarted.
2017-04-09 15:28 GMT+08:00 吴朱华 <ik...@gmail.com>:
> During 10-15sec loading, from top, we only can see 2-3sec more than
> 100%-200% java usage, other than that there is nothing serious working,
> and we will attach profile once we have it, and this question has been
> haunted us for year.
>
> 2017-04-09 15:13 GMT+08:00 吴朱华 <ik...@gmail.com>:
>
>> Plus the schema we using is simple
>>
>> 2017-04-09 15:11 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>
>>> The current version using early 2016, the metadata loading is 10-15sec.
>>> We haven't try the latest version, we hope the issue has been solved^_^
>>>
>>> 2017-04-07 14:08 GMT+08:00 Alex Behm <al...@cloudera.com>:
>>>
>>>> What was your Impala version before and what is it now?
>>>>
>>>> How fast was it before and how fast is it now?
>>>>
>>>> On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
>>>>
>>>>> Hi guys:
>>>>>
>>>>> Is there any change on metadata loading? The metadata loading used to
>>>>> 10sec.
>>>>>
>>>>> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>
>>>>>> thx^_^
>>>>>>
>>>>>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>>>>>
>>>>>>> If your build does not have runtime filters (which are a little more
>>>>>>> than a year old), then the answer is yes: you should upgrade.
>>>>>>>
>>>>>>> Performance in general has been improving steadily over the last
>>>>>>> year.
>>>>>>>
>>>>>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>>>>>
>>>>>>>> The question is there any big join perf related improvement has
>>>>>>>> implemented? Thx
>>>>>>>>
>>>>>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>>>>
>>>>>>>> > Hi guys:
>>>>>>>> >
>>>>>>>> > I am currently using my one year old build (I guess 2016.3
>>>>>>>> CDH5-Trunk),
>>>>>>>> > now I am facing a lot of join query situation(two big table
>>>>>>>> joins), do I
>>>>>>>> > need to upgrade my one year old build for potential join perf
>>>>>>>> improvement?
>>>>>>>> > Thx at advance^_^
>>>>>>>> >
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by 吴朱华 <ik...@gmail.com>.
During 10-15sec loading, from top, we only can see 2-3sec more than
100%-200% java usage, other than that there is nothing serious working, and
we will attach profile once we have it, and this question has been haunted
us for year.
2017-04-09 15:13 GMT+08:00 吴朱华 <ik...@gmail.com>:
> Plus the schema we using is simple
>
> 2017-04-09 15:11 GMT+08:00 吴朱华 <ik...@gmail.com>:
>
>> The current version using early 2016, the metadata loading is 10-15sec.
>> We haven't try the latest version, we hope the issue has been solved^_^
>>
>> 2017-04-07 14:08 GMT+08:00 Alex Behm <al...@cloudera.com>:
>>
>>> What was your Impala version before and what is it now?
>>>
>>> How fast was it before and how fast is it now?
>>>
>>> On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
>>>
>>>> Hi guys:
>>>>
>>>> Is there any change on metadata loading? The metadata loading used to
>>>> 10sec.
>>>>
>>>> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>
>>>>> thx^_^
>>>>>
>>>>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>>>>
>>>>>> If your build does not have runtime filters (which are a little more
>>>>>> than a year old), then the answer is yes: you should upgrade.
>>>>>>
>>>>>> Performance in general has been improving steadily over the last year.
>>>>>>
>>>>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>>>>
>>>>>>> The question is there any big join perf related improvement has
>>>>>>> implemented? Thx
>>>>>>>
>>>>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>>>
>>>>>>> > Hi guys:
>>>>>>> >
>>>>>>> > I am currently using my one year old build (I guess 2016.3
>>>>>>> CDH5-Trunk),
>>>>>>> > now I am facing a lot of join query situation(two big table
>>>>>>> joins), do I
>>>>>>> > need to upgrade my one year old build for potential join perf
>>>>>>> improvement?
>>>>>>> > Thx at advance^_^
>>>>>>> >
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by 吴朱华 <ik...@gmail.com>.
Plus the schema we using is simple
2017-04-09 15:11 GMT+08:00 吴朱华 <ik...@gmail.com>:
> The current version using early 2016, the metadata loading is 10-15sec.
> We haven't try the latest version, we hope the issue has been solved^_^
>
> 2017-04-07 14:08 GMT+08:00 Alex Behm <al...@cloudera.com>:
>
>> What was your Impala version before and what is it now?
>>
>> How fast was it before and how fast is it now?
>>
>> On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
>>
>>> Hi guys:
>>>
>>> Is there any change on metadata loading? The metadata loading used to
>>> 10sec.
>>>
>>> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>
>>>> thx^_^
>>>>
>>>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>>>
>>>>> If your build does not have runtime filters (which are a little more
>>>>> than a year old), then the answer is yes: you should upgrade.
>>>>>
>>>>> Performance in general has been improving steadily over the last year.
>>>>>
>>>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>>>
>>>>>> The question is there any big join perf related improvement has
>>>>>> implemented? Thx
>>>>>>
>>>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>>
>>>>>> > Hi guys:
>>>>>> >
>>>>>> > I am currently using my one year old build (I guess 2016.3
>>>>>> CDH5-Trunk),
>>>>>> > now I am facing a lot of join query situation(two big table joins),
>>>>>> do I
>>>>>> > need to upgrade my one year old build for potential join perf
>>>>>> improvement?
>>>>>> > Thx at advance^_^
>>>>>> >
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by 吴朱华 <ik...@gmail.com>.
The current version using early 2016, the metadata loading is 10-15sec.
We haven't try the latest version, we hope the issue has been solved^_^
2017-04-07 14:08 GMT+08:00 Alex Behm <al...@cloudera.com>:
> What was your Impala version before and what is it now?
>
> How fast was it before and how fast is it now?
>
> On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
>
>> Hi guys:
>>
>> Is there any change on metadata loading? The metadata loading used to
>> 10sec.
>>
>> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>
>>> thx^_^
>>>
>>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>>
>>>> If your build does not have runtime filters (which are a little more
>>>> than a year old), then the answer is yes: you should upgrade.
>>>>
>>>> Performance in general has been improving steadily over the last year.
>>>>
>>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>>
>>>>> The question is there any big join perf related improvement has
>>>>> implemented? Thx
>>>>>
>>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>>
>>>>> > Hi guys:
>>>>> >
>>>>> > I am currently using my one year old build (I guess 2016.3
>>>>> CDH5-Trunk),
>>>>> > now I am facing a lot of join query situation(two big table joins),
>>>>> do I
>>>>> > need to upgrade my one year old build for potential join perf
>>>>> improvement?
>>>>> > Thx at advance^_^
>>>>> >
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by Alex Behm <al...@cloudera.com>.
What was your Impala version before and what is it now?
How fast was it before and how fast is it now?
On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
> Hi guys:
>
> Is there any change on metadata loading? The metadata loading used to
> 10sec.
>
> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>
>> thx^_^
>>
>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>
>>> If your build does not have runtime filters (which are a little more
>>> than a year old), then the answer is yes: you should upgrade.
>>>
>>> Performance in general has been improving steadily over the last year.
>>>
>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>
>>>> The question is there any big join perf related improvement has
>>>> implemented? Thx
>>>>
>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>
>>>> > Hi guys:
>>>> >
>>>> > I am currently using my one year old build (I guess 2016.3
>>>> CDH5-Trunk),
>>>> > now I am facing a lot of join query situation(two big table joins),
>>>> do I
>>>> > need to upgrade my one year old build for potential join perf
>>>> improvement?
>>>> > Thx at advance^_^
>>>> >
>>>>
>>>
>>>
>>
>
Re: Need to upgrade my one year old build for potential join perf improvement?
Posted by Alex Behm <al...@cloudera.com>.
What was your Impala version before and what is it now?
How fast was it before and how fast is it now?
On Thu, Apr 6, 2017 at 9:16 PM, 吴朱华 <ik...@gmail.com> wrote:
> Hi guys:
>
> Is there any change on metadata loading? The metadata loading used to
> 10sec.
>
> 2017-03-23 12:42 GMT+08:00 吴朱华 <ik...@gmail.com>:
>
>> thx^_^
>>
>> 2017-03-23 11:51 GMT+08:00 Henry Robinson <he...@apache.org>:
>>
>>> If your build does not have runtime filters (which are a little more
>>> than a year old), then the answer is yes: you should upgrade.
>>>
>>> Performance in general has been improving steadily over the last year.
>>>
>>> On 22 March 2017 at 20:36, 吴朱华 <ik...@gmail.com> wrote:
>>>
>>>> The question is there any big join perf related improvement has
>>>> implemented? Thx
>>>>
>>>> 2017-03-23 11:34 GMT+08:00 吴朱华 <ik...@gmail.com>:
>>>>
>>>> > Hi guys:
>>>> >
>>>> > I am currently using my one year old build (I guess 2016.3
>>>> CDH5-Trunk),
>>>> > now I am facing a lot of join query situation(two big table joins),
>>>> do I
>>>> > need to upgrade my one year old build for potential join perf
>>>> improvement?
>>>> > Thx at advance^_^
>>>> >
>>>>
>>>
>>>
>>
>