giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maja Kabiljo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GIRAPH-397) We should have copies of aggregators per thread to avoid synchronizing on aggregate()
Date Mon, 05 Nov 2012 19:02:12 GMT

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

Maja Kabiljo updated GIRAPH-397:
--------------------------------

    Attachment: GIRAPH-397.patch

Eli, thanks for looking! I don't think it makes a big difference, since there are just a few
extra empty maps, but ok, I turned it off by default. That's the only change in the patch.
Will commit by the end of the day if nobody objects.
                
> We should have copies of aggregators per thread to avoid synchronizing on aggregate()
> -------------------------------------------------------------------------------------
>
>                 Key: GIRAPH-397
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-397
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Maja Kabiljo
>            Assignee: Maja Kabiljo
>            Priority: Minor
>         Attachments: GIRAPH-397.patch, GIRAPH-397.patch
>
>
> Fixing one of TODOs from GIRAPH-273. Adding copies of aggregators for each thread allows
us not to have to synchronize on each aggregate call. Aggregated values from each thread can
be aggregated together after computation is finished.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message