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

Posted to dev@phoenix.apache.org by "Jeffrey Zhong (JIRA)" <ji...@apache.org> on 2014/03/10 23:55:42 UTC

[jira] [Commented] (PHOENIX-131) Incorrect determination of total available memory

    [ https://issues.apache.org/jira/browse/PHOENIX-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926386#comment-13926386 ] 

Jeffrey Zhong commented on PHOENIX-131:
---------------------------------------

Please also check the fix into master & 4.0 branch. Thanks.

> Incorrect determination of total available memory
> -------------------------------------------------
>
>                 Key: PHOENIX-131
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-131
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: totalMem.patch
>
>
> Instead of using Runtime.getRuntime().maxMemory() to get the total memory, we were using Runtime.getRuntime().totalMemory(). Fixing this and we'll have *a lot* more memory available for GROUP BY and joins.



--
This message was sent by Atlassian JIRA
(v6.2#6252)