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

Posted to issues@beam.apache.org by "Robert Burke (JIRA)" <ji...@apache.org> on 2019/01/23 23:55:00 UTC

[jira] [Commented] (BEAM-4852) [Go SDK] Beam should not retain the symbol table after function resolution

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

Robert Burke commented on BEAM-4852:
------------------------------------

The code generator starcgen does all appropriate registrations for the specified user types, avoiding the symbol table altogether, significantly reducing the priority/necessity of this for pipelines that need to be perfomant.

> [Go SDK] Beam should not retain the symbol table after function resolution
> --------------------------------------------------------------------------
>
>                 Key: BEAM-4852
>                 URL: https://issues.apache.org/jira/browse/BEAM-4852
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>            Reporter: Robert Burke
>            Assignee: Robert Burke
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> In some instances, Beam Go requires introspecting the symbol table for the binary to resolve functions. However it may be possible to cache these results for all applicable functions, and then allow the table to be garbage collected.
> The table represents a large heap cost that is retained for the lifetime of a job.
> A secondary goal would be to avoid incurring the cost entirely when there's nothing to look up for a job. Eg for unit tests, or ancillary uses of the beam SDK (eg. migrating from some other system to beam shouldn't incur the cost when the old system is being used, just because beam is linked in and triggered by a runtime switch).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)