Details
Major Description
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.