beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <>
Subject [jira] [Commented] (BEAM-3572) Reduce inefficient allocations in coders
Date Tue, 30 Jan 2018 21:56:00 GMT


Kenneth Knowles commented on BEAM-3572:

My reading of {{IterableLikeCoder}} is that it is stateless. Did I miss something?

> Reduce inefficient allocations in coders
> ----------------------------------------
>                 Key: BEAM-3572
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Bill Neubauer
>            Assignee: Bill Neubauer
>            Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> BufferedElementCountingOutputStream's constructor allocates a new buffer to wrap the
input OutputStream. This gets called on each invocation of encode() from IterableLikeCoder.
Since Coder is designed to be stateless, but this buffer holds state and isn't threadsafe,
we can't just have the caller manage the buffer. Modifying the constructor to use a pool of
buffers to reduce the number of allocations will help performance.

This message was sent by Atlassian JIRA

View raw message