Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Tue, 16 Apr 2013 11:25:19 +0000 (UTC)
From: "Leo Romanoff (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12638536.1363971445284.173089.1366111519049@arcas>
In-Reply-To: <JIRA.12638536.1363971445284@arcas>
References: <JIRA.12638536.1363971445284@arcas>
Subject: [jira] [Updated] (AVRO-1282) Make use of the sun.misc.Unsafe class
 during serialization if a JDK supports it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Leo Romanoff updated AVRO-1282:
-------------------------------

    Status: Patch Available  (was: Open)

I just submitted a patch that implements Unsafe-based serialization/deserialization in case of reflection-based (de)serializers. It also includes a performance test. 
You can run it using 
 mvn exec:java -Dexec.mainClass="org.apache.avro.io.Perf" -Dexec.classpathScope=test -Dexec.args="-REFr"

or 

 mvn exec:java -Dexec.mainClass="org.apache.avro.io.Perf" -Dexec.classpathScope=test -Dexec.args="-reflect"

On my machine I get 5x performance boost using Unsafe approach.
                
> Make use of the sun.misc.Unsafe class during serialization if a JDK supports it
> -------------------------------------------------------------------------------
>
>                 Key: AVRO-1282
>                 URL: https://issues.apache.org/jira/browse/AVRO-1282
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.4
>            Reporter: Leo Romanoff
>            Priority: Minor
>         Attachments: avro-1282-v1.patch
>
>
> Unsafe can be used to significantly speed up serialization process, if a JDK implementation supports java.misc.Unsafe properly. Most JDKs running on PCs support it. Some platforms like Android lack a proper support for Unsafe yet.
> There are two possibilities to use Unsafe for serialization:
> 1) Very quick access to the fields of objects. It is way faster than with the reflection-based approach using Field.get/set
> 2) Input and Output streams can be using Unsafe to perform very quick input/output.
>  
> 3) More over, Unsafe makes it possible to serialize to/deserialize from off-heap memory directly and very quickly, without any intermediate buffers allocated on heap. There is virtually no overhead compared to the usual byte arrays.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira