Kylin does not cache a fast query, which returns in 2 seconds. Think it is
cheap to execute again and does not worth to cache.
On Tue, Sep 26, 2017 at 10:16 PM, 446463...@qq.com <446463...@qq.com> wrote:
> Hi All:
> I meet a problem when I query in kylin.
> I found that some query hit storage
Hi All:
I meet a problem when I query in kylin.
I found that some query hit storage cache when I tried it twice and another
query not although I did query twice.
have someone meet this before?
environment:CDH5.8 ,kylin2.0.0
446463...@qq.com
does your test query contain any aggregations? like min max sum. If no
aggregation exists, then the query will seek to scan base cuboid, which is
nearly as large as raw data in some bad cases.
On Fri, Aug 19, 2016 at 11:10 AM, Mars J wrote:
> just 'select A,B from Fact
just 'select A,B from Fact f left join dima a on f.no=a.no...', when I
query this, it needs 10+s, then the same sql will return result in 0.0s,
but when I change the limit N or any column behind 'select' and 'group by'
and join table ,it costs more than 10+s again.
the source records in fact and
Performance troubleshoot is complicated and requires much information. If
you can share a diagnosis pack, people maybe able to help.
On Sat, Aug 13, 2016 at 10:32 PM, Yiming Liu
wrote:
> What's kind of queries? How many records supposed to be returned? Could you
> send
Hi,
I have run Kylin 1.5.2.1 and build a cube successfully,the cube size is
3.2G for fact table and dimensional table have 1.5 million records
seperately.HTable count is about 200 billion.
My Cube Design includes 3 Derived Dims and 5 Normal Dims which formed a
hierachy dim in agg. Rowkeys