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

Posted to dev@giraph.apache.org by "Hassan Eslami (JIRA)" <ji...@apache.org> on 2016/06/15 18:14:09 UTC

[jira] [Commented] (GIRAPH-1072) Improve metrics reported in out-of-core computation

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

Hassan Eslami commented on GIRAPH-1072:
---------------------------------------

https://reviews.facebook.net/D59451

> Improve metrics reported in out-of-core computation
> ---------------------------------------------------
>
>                 Key: GIRAPH-1072
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1072
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Hassan Eslami
>            Assignee: Hassan Eslami
>
> Currently, out-of-core infrastructure reports some metrics as part of master/worker log, and also as part of Hadoop job counters. There is a need to show, for a specific out-of-core policy, how much of the graph were kept in memory at the worst (i.e. memory heaviest) moment in the execution. Particularly, a user would be interested in knowing how many more machines the job should be run on, so that the entire execution fits in memory.



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