[
https://issues.apache.org/jira/browse/KYLIN-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358585#comment-15358585
]
hongbin ma commented on KYLIN-1843:
-----------------------------------
I don't quite understand, do you mean result set caching? currently the cache
is caching each result row. How can one tell which dimension is useful and
which is not? After all, all of the cached dimensions exist in the "select"
clause
> LRU cache for in memory dimensions
> ----------------------------------
>
> Key: KYLIN-1843
> URL: https://issues.apache.org/jira/browse/KYLIN-1843
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
> Affects Versions: v1.2, v1.5.2
> Reporter: Abhilash L L
> Assignee: liyang
>
> The dimensions are kept in memory to fill up the result set.
> Now as and when more cubes are created, all the dimensions keep accumulating
> in the memory
> This means tomcat memory requirements always keep increasing
> It would help if less frequently used dimensions are swapped out to keep
> memory in check.
> We can have a Cache Manager which gets to decide which dimensions are kept in
> memory and brings in as and when its required. The size of the cache should
> be tuneable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
