apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-606) Suggestion: Optimise Kryo Output
Date Fri, 27 Jan 2017 19:21:24 GMT

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

ASF GitHub Bot commented on APEXCORE-606:
-----------------------------------------

Github user brightchen closed the pull request at:

    https://github.com/apache/apex-core/pull/455


> Suggestion: Optimise Kryo Output
> --------------------------------
>
>                 Key: APEXCORE-606
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-606
>             Project: Apache Apex Core
>          Issue Type: New Feature
>            Reporter: bright chen
>            Assignee: bright chen
>
> The kryo Output has some limitation
>   - The size of the data is limited. kryo write data to the buffer, it will throw the
overflow exception if the data exceed the size
>   - The Output.toBytes() will copy the data to temporary buffer and output, it will 
decrease the performance and introduce garbage collection.
> When I was tuning Spillable Data structure and Manage State. I create a mechanism to
share and reuse the memory to avoid above problem.  And it can be reused in core serialization
with small change. Please see jira: https://issues.apache.org/jira/browse/APEXMALHAR-2190



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message