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

Posted to issues@arrow.apache.org by "Ji Liu (Jira)" <ji...@apache.org> on 2019/09/18 06:00:00 UTC

[jira] [Assigned] (ARROW-6593) [Java] Experiment with performance difference of avoiding the use of Avro Decoder

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

Ji Liu reassigned ARROW-6593:
-----------------------------

    Assignee: Ji Liu

> [Java] Experiment with performance difference of avoiding the use of Avro Decoder
> ---------------------------------------------------------------------------------
>
>                 Key: ARROW-6593
>                 URL: https://issues.apache.org/jira/browse/ARROW-6593
>             Project: Apache Arrow
>          Issue Type: Sub-task
>          Components: Java
>            Reporter: Micah Kornfield
>            Assignee: Ji Liu
>            Priority: Major
>              Labels: avro
>
> It has been posited that the Decoder object (and on-heap work in general) is potentially slow for decoding.
>  
> The scope of this Jira is to add a new method that instead of consuming from Decoder, consumes directly from a ByteBuffer.  In order to this we there needs to be utility classes for zig-zag decoding (one might existing in avro) from a ByteBuffer.
>  
> This is esentially rewriting logic in the decoder to work directly against a bytebuffer and then measure if there is a meaningful performance impact.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)