You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2015/09/29 08:41:04 UTC

[jira] [Resolved] (KYLIN-1048) CPU and memory killer in Cuboid.findById()

     [ https://issues.apache.org/jira/browse/KYLIN-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaofeng SHI resolved KYLIN-1048.
---------------------------------
    Resolution: Fixed

> CPU and memory killer in Cuboid.findById()
> ------------------------------------------
>
>                 Key: KYLIN-1048
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1048
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Metadata
>    Affects Versions: v1.0, v0.7.2, v0.7.1
>            Reporter: Shaofeng SHI
>            Assignee: Shaofeng SHI
>             Fix For: v2.0, v1.1
>
>
> In an cube which has 37 dimensions with a couple of aggregation groups (and each group has hierarchy), when a SQL which has columns cross aggregation groups, it couldn't be returned in time, the CPU will very high and memory usage increases also, finally cause Kylin server crashed with OutOfMemory error.
> After doing some analysis and profiling, identified that when the cube is a sparse partial cube, the performance in Cuboid.findById() is bad,  which will take much CPU and memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)