Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Fri, 22 Mar 2013 16:21:25 +0000 (UTC)
From: =?utf-8?Q?Holger_Hoffst=C3=A4tte_=28JIRA=29?= <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12638314.1363884679457.36445.1363969285922@arcas>
In-Reply-To: <JIRA.12638314.1363884679457@arcas>
References: <JIRA.12638314.1363884679457@arcas>
Subject: [jira] [Commented] (AVRO-1277) Improve performance of
 reflection-based serializers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AVRO-1277?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13610=
609#comment-13610609 ]=20

Holger Hoffst=C3=A4tte commented on AVRO-1277:
-----------------------------------------

Doug, thanks for addressing my concerns. I agree that making a client respo=
nsible for managing ReflectData instances and passing them into any created=
 readers/writers fixes practically every possible lifecycle issue, so +1. A=
lso getting rid of the static instance is useful for other purposes (less l=
eaks in testing etc.) so +1 on all of that. Thanks!

               =20
> Improve performance of reflection-based serializers
> ---------------------------------------------------
>
>                 Key: AVRO-1277
>                 URL: https://issues.apache.org/jira/browse/AVRO-1277
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.4
>            Reporter: Leo Romanoff
>            Priority: Minor
>         Attachments: AVRO-1277.patch, AVRO-1277-v2.patch
>
>
> I've played a bit with Avro serialization based on reflection, i.e. with =
the classes from org.apache.avro.generic package.
> It works fine in this mode, but is rather slow compared to such framework=
s like protostuff or kryo.
> Quick look at the source code has shown that a lot of reflection-based op=
erations and class lookups are not cached. And such operations are usually =
pretty expensive when executed by a JVM.=20
> So I changed some of org.apache.avro.generic classes, introduced caching =
and a few other optimizations. Now it seems to perform much better.

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