Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Message-ID: <5720601.258521281462797158.JavaMail.jira@thor>
Date: Tue, 10 Aug 2010 13:53:17 -0400 (EDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Subject: [jira] Updated: (AVRO-557) Speed up one-time data decoding
In-Reply-To: <15151670.142631275509552272.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Doug Cutting updated AVRO-557:
------------------------------

    Attachment: AVRO-557.patch

Okay, here's a winner.  This one caches the entire ResolvingDecoder, not just its resolver.

GenericReaderOneTimeUsageTest: 1793 ms, 2.3228573849749345 million entries/sec.  0.010871407417979413 million bytes/sec

Kevin, can you confirm whether an identity-based cache of schemas works for your use case?  If not, we could try this with an equals-hash and perhaps optimize Schema#hashCode().

> Speed up one-time data decoding
> -------------------------------
>
>                 Key: AVRO-557
>                 URL: https://issues.apache.org/jira/browse/AVRO-557
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.3.2
>            Reporter: Kevin Oliver
>            Assignee: Kevin Oliver
>             Fix For: 1.4.0
>
>         Attachments: AVRO-557.patch, AVRO-557.patch, AVRO-557.patch
>
>
> There are big gains to be had in performance when using a BinaryDecoder and a GenericDatumReader just one time. This is due to the relatively expensive parsing and initialization that came with 1.3. Patch with example code and a Perf harness to follow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.