RE: Performance degradation on query analysis

2019-09-27 Thread Stepan Migunov
@phoenix.apache.org Subject: Re: Performance degradation on query analysis Did you change your configuration to prevent compactions from regularly happening, Stepan? By default, you should have a major compaction run weekly which would have fixed this for you, although minor compactions would have run

Re: Performance degradation on query analysis

2019-09-24 Thread Josh Elser
l Message- From: Josh Elser [mailto:els...@apache.org <mailto:els...@apache.org>] Sent: Tuesday, September 17, 2019 5:16 PM To: user@phoenix.apache.org <mailto:user@phoenix.apache.org> Subject: Re: Performance degradation on query analysis Can you share th

Re: Performance degradation on query analysis

2019-09-19 Thread Ankit Singhal
; Sent: Tuesday, September 17, 2019 5:16 PM > To: user@phoenix.apache.org > Subject: Re: Performance degradation on query analysis > > Can you share the output you see from the EXPLAIN? Does it differ between > times it's "fast" and times it's "slow"? > > Sharing the t

RE: Performance degradation on query analysis

2019-09-19 Thread Stepan Migunov
: Josh Elser [mailto:els...@apache.org] Sent: Tuesday, September 17, 2019 5:16 PM To: user@phoenix.apache.org Subject: Re: Performance degradation on query analysis Can you share the output you see from the EXPLAIN? Does it differ between times it's "fast" and times it's "slow"?

Re: Performance degradation on query analysis

2019-09-17 Thread Josh Elser
Can you share the output you see from the EXPLAIN? Does it differ between times it's "fast" and times it's "slow"? Sharing the table(s) DDL statements would also help, along with the shape and version of your cluster (e.g. Apache Phoenix 4.14.2 with 8 RegionServers). Spit-balling ideas:

Performance degradation on query analysis

2019-09-17 Thread Stepan Migunov
Hi We have an issue with our production environment - from time to time we notice a significant performance degradation for some queries. The strange thing is that the EXPLAIN operator for these queries takes the same time as queries execution (5 minutes or more). So, I guess, the issue is