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 2019/01/24 19:12:00 UTC
[jira] [Updated] (BEAM-6503)
PCollectionViews$SimplePCollectionView.hashCode once again allocates memory
(fix reverted, then fixed again)
[ https://issues.apache.org/jira/browse/BEAM-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-6503:
----------------------------------
Fix Version/s: (was: 2.9.0)
> PCollectionViews$SimplePCollectionView.hashCode once again allocates memory (fix reverted, then fixed again)
> ------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-6503
> URL: https://issues.apache.org/jira/browse/BEAM-6503
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Affects Versions: 2.8.0
> Reporter: Vojtech Janota
> Assignee: Vojtech Janota
> Priority: Trivial
>
> I'm currently profiling memory consumption of our Beam pipeline and have noticed that
> org.apache.beam.sdk.values.PCollectionViews$SimplePCollectionView.hashCode()
> makes noticeable heap allocations. The implementation is:
> return Objects.hash(tag);
> That itself translates to:
> return Arrays.hashCode(values);
> Which performs implicit array creation in order to call:
> public static int Arrays.hashCode(Object a[]);
> Instead of the helper call, doing simple:
> tag.hashCode();
> Seems more appropriate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)