kylin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <>
Subject Re: cube building VS cognos
Date Mon, 02 Mar 2015 05:47:43 GMT
This sounds like cognos is actually just building a few, possibly just one,
of the more detailed cubes expecting that queries will roll these up to get
effect of many of the less detailed cubes.  That is, it may not be building
all of the cubes requested.

Kylin, on the other hand, seems to be building up all requested cubes with
no optimization being imposed.

Note that these are my impressions based on seeing how new open source
software often behaves relative to older, more established alternatives,
not anything based on concrete information.  I look forward to being
contradicted by facts.

On Mon, Mar 2, 2015 at 3:59 AM, 王西斌 <> wrote:

> Hi
> I've done some test for comparison with cognos which we used for olap.
> Below is one case:
> Fact table size: 500M
> Dimension: 19( 16 derived, 3 normal)
> Measure: 56
> Cognos building this cube in about one hour with a 1.2G cube file.
> While in kylin, cube size is already up to 64G with 10 Dimensions and 20
> Measures. If i understand right, the cube size will double at least for
> each additional dimension. As to the test case, cube size is estimated in
> TB which is beyond our expectations greatly.
> So, is there any test report we can refer to for comparison with
> traditional olap tools like cognos, if so, please let me know, it will be
> very helpful.
> Looking forward to reply.
> Thanks

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message