giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dionysios Logothetis (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (GIRAPH-1150) Fixing MemoryEstimatorOracle
Date Tue, 12 May 2020 18:09:00 GMT

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

Dionysios Logothetis resolved GIRAPH-1150.
------------------------------------------
    Resolution: Fixed

> Fixing MemoryEstimatorOracle
> ----------------------------
>
>                 Key: GIRAPH-1150
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1150
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Hassan Eslami
>            Assignee: Hassan Eslami
>            Priority: Major
>
> * Once the OOC is at OFFLAODING state, it may offload data to disk indefinitely. We should
call GC manually and get OOC out of OFFLOADING if anything has changed in computation/communication
pattern.
> * Fixes a "if" statement which entirely disabled regression for memory estimation.
> * Interleaving of in resetting and calculating memory estimation potentially can cause
data race.
> * The superstep count in memory estimator was not coherent throughout the calculation.
> * Sometime the memory estimator's accuracy is not good. We should fall back to a threshold-based
scheme relying on a more pessimistic memory usage report (such as the one given by JVM --
memory usage includes garbage data too, but it can be used as a pessimistic estimate, as it
is currently used in ThresholdBasedOracle).
> More tuning is needed for a smooth memory estimation mechanism.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message