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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:03 UTC

[jira] [Updated] (BEAM-4468) Go SDK-Tune in memory pre-combine caching for Lifted Combines.

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

Kenneth Knowles updated BEAM-4468:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Go SDK-Tune in memory pre-combine caching for Lifted Combines.
> --------------------------------------------------------------
>
>                 Key: BEAM-4468
>                 URL: https://issues.apache.org/jira/browse/BEAM-4468
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>            Reporter: Robert Burke
>            Priority: P3
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Requires [BEAM-4276|https://issues.apache.org/jira/browse/BEAM-4276] to be completed first.
> Additional performance tweaks to the in memory per-key accumulator cache during the pre-combine phase of a lifted combine.
> This can include any of
>  * capping the number of key-accumulator in the cache, and draining them eagerly after x elements seen, or evicting keys by some heuristic after the cache has seen X distinct keys.
>  * providing a counter on cache size (key/element counts) exposable through the metrics interface or another runner standard counter, to permit observing the cache's status, especially if it could grow without bound within a bundle.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)