ames Taylor [mailto:jamestay...@apache.org]
Sent: Tuesday, March 03, 2015 11:18 PM
To: user
Subject: Re: Update statistics made query 2-3x slower
Ah, so you actually *are* in the situation I mentioned (i.e. you had *NOT* run
a major compaction yet on the table, but you had run an UPDATE STATISTICS). If
299955368042 , 40 ,
> 0.672780654907 , 1 , 1 , 13 , 272 , 272 , 1 , 1 , 27 , 7 , 5 , 1 , 1 ,
>
> 1 , 11 , 30 , 2 , 4 , 1 , 1 , 3 , 3 , 8 , 3 , 5 , 3 , 16 , 1 , 6 , 1 , 1
> , 1 , 1 , 4 , 184 , 4 , 3 , 8 , 2 , 5 , 666 , 1 , 1 , 5 , 1 , 1 , 1 , 2 ,
>
> 1 , 5 , 5 , 1 , 1 , 3 , 3 , 4 ,
, Constantin (GfK)
Subject: Re: Update statistics made query 2-3x slower
Constantin,
I've filed PHOENIX-1693 for this issue, as we seem to be seeing a similar
phenomena too. It seems to only occur if we've never run a major compaction on
the table, though. Is that the case for you as we
to:constantin.ciure...@gfk.com>]
Sent: Monday, February 16, 2015 3:17 PM
To: user@phoenix.apache.org<mailto:user@phoenix.apache.org>
Subject: RE: Update statistics made query 2-3x slower
Hello,
I forgot to add this info:
3. There are just a few requests while running select count(*) –
mailto:constantin.ciure...@gfk.com]
> *Sent:* Monday, February 16, 2015 3:17 PM
>
> *To:* user@phoenix.apache.org
> *Subject:* RE: Update statistics made query 2-3x slower
>
>
>
> Hello,
>
>
>
> I forgot to add this info:
>
>
>
> 3. There are just a few req
nday, February 16, 2015 10:31 AM
To: user@phoenix.apache.org<mailto:user@phoenix.apache.org>
Subject: RE: Update statistics made query 2-3x slower
Hi Mujtaba,
1. Update statistics - was executed after loading the data in the table
(and after first select count(*)… of course).
2
|
| SERVER AGGREGATE INTO SINGLE ROW |
+--+
3 rows selected (0.287 seconds)
Thank you,
Constantin
From: Mujtaba Chohan [mailto:mujt...@apache.org]
Sent: Friday, February 13, 2015 7:21 PM
To: user@phoenix.apache.org<mailto:user@phoenix.apache.org>
Subject: R
rows selected (0.287 seconds)
Thank you,
Constantin
From: Mujtaba Chohan [mailto:mujt...@apache.org]
Sent: Friday, February 13, 2015 7:21 PM
To: user@phoenix.apache.org
Subject: Re: Update statistics made query 2-3x slower
Hi Constantin,
This in useful info. Just to clarify slowdown that you see
gt;
>
> *From:* Mujtaba Chohan [mailto:mujt...@apache.org]
> *Sent:* Thursday, February 12, 2015 9:20 PM
>
> *To:* user@phoenix.apache.org
> *Subject:* Re: Update statistics made query 2-3x slower
>
>
>
> Constantin - If possible can you please share your schema, approx.
ory
in my opinion).
Regards,
Constantin
From: Mujtaba Chohan [mailto:mujt...@apache.org]
Sent: Thursday, February 12, 2015 9:20 PM
To: user@phoenix.apache.org
Subject: Re: Update statistics made query 2-3x slower
Constantin - If possible can you please share your schema, approx. row/colu
]
Sent: Friday, February 13, 2015 1:50 AM
To: user@phoenix.apache.org
Subject: Re: Update statistics made query 2-3x slower
Constantin - If possible can you please share your schema, approx. row/columns
width, number of region servers in your cluster plus their heap size,
HBase/Phoenix version and
>
>
>
> *From:* Mujtaba Chohan [mailto:mujt...@apache.org]
> *Sent:* Wednesday, February 11, 2015 8:54 PM
> *To:* user@phoenix.apache.org
> *Subject:* Re: Update statistics made query 2-3x slower
>
>
>
> To compare performance without stats, try deleting related rows from
&g
(especially if the tombstones for
deleted rows are still there – ie. not compacted yet).
Constantin
From: Mujtaba Chohan [mailto:mujt...@apache.org]
Sent: Wednesday, February 11, 2015 8:54 PM
To: user@phoenix.apache.org
Subject: Re: Update statistics made query 2-3x slower
To compare performance
To compare performance without stats, try deleting related rows from
SYSTEM.STATS or an easier way, just truncate SYSTEM.STATS table from HBase
shell and restart your region servers.
//mujtaba
On Wed, Feb 11, 2015 at 10:29 AM, Vasudevan, Ramkrishna S <
ramkrishna.s.vasude...@intel.com> wrote:
>
Hi Constantin
Before I could explain on the slowness part let me answer your 2nd question,
Phoenix is on top of HBase. HBase is a distributed NoSQL DB. So the data that
is residing inside logical entities called regions are spread across different
nodes (region servers). There is nothing like
15 matches
Mail list logo
