giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hassan Eslami (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-1027) Improve flow-control on sender side
Date Mon, 04 Apr 2016 23:42:25 GMT

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

Hassan Eslami commented on GIRAPH-1027:
---------------------------------------

Thanks Dionysios and Maja for reviewing and committing the diff.

> Improve flow-control on sender side
> -----------------------------------
>
>                 Key: GIRAPH-1027
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1027
>             Project: Giraph
>          Issue Type: Improvement
>          Components: graph
>            Reporter: Hassan Eslami
>            Assignee: Hassan Eslami
>
> Currently, a sender worker will keep all open requests (and optionally up to a certain
number of total open requests) in its own memory. This behavior may cause high memory usage
in sender side. Also, since messages can arrive to a worker at an arbitrary rate, receiver
may not have the ability to handle all incoming messages, hence we may see a large memory
footprint in receiver as well. This diff addresses the problem by limiting the number of open
requests per worker in sender side. Also, it provides a cache of unsent requests on sender
in case the sender already sent enough messages to another worker but has not received any
response back.



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

Mime
View raw message