Return-Path: X-Original-To: apmail-avro-user-archive@www.apache.org Delivered-To: apmail-avro-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 534266CED for ; Thu, 2 Jun 2011 00:49:09 +0000 (UTC) Received: (qmail 79172 invoked by uid 500); 2 Jun 2011 00:49:09 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 79138 invoked by uid 500); 2 Jun 2011 00:49:09 -0000 Mailing-List: contact user-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@avro.apache.org Delivered-To: mailing list user@avro.apache.org Received: (qmail 79130 invoked by uid 99); 2 Jun 2011 00:49:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jun 2011 00:49:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tsaloranta@gmail.com designates 209.85.215.171 as permitted sender) Received: from [209.85.215.171] (HELO mail-ey0-f171.google.com) (209.85.215.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jun 2011 00:49:04 +0000 Received: by eydd26 with SMTP id d26so179842eyd.30 for ; Wed, 01 Jun 2011 17:48:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=yQXMkGxhkSG+HD+XVJXOxlZ/vufbIdF2o4lasPMV8R8=; b=D1NW+POfJIlkEVyVJeJ6l++CA5vspQyGHJ9mRg+SgfsqHoQBH+wGav3guE4GHcWBi7 QmwhZ5IDWgrcApK7Aw8SADh6+nFDx6t/w0FTBeUNsXrf9SREmev5YOJC06Qzs7tuU7cq +ckcUmIH0r3vxzkU/9exhV7Jf2e/D6Ts7f93o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=kWCytSwhc1y/INxaxWykij0rLIfMR/CAHfZMxe+JMa2+a4SxxN0hvJKLIRI8R3AEQ0 rYm5OnpyvwPdhz9ccDXpYHOfl78vUHV2VAy4uryvoxO+DQV4HubncMMz/nEFRH5On0XT xop1JKjZZAdTtMjq+yrhQekWF7Eg5tIJhuFoY= MIME-Version: 1.0 Received: by 10.14.9.155 with SMTP id 27mr38599eet.237.1306975722751; Wed, 01 Jun 2011 17:48:42 -0700 (PDT) Received: by 10.14.29.72 with HTTP; Wed, 1 Jun 2011 17:48:42 -0700 (PDT) In-Reply-To: References: Date: Wed, 1 Jun 2011 17:48:42 -0700 Message-ID: Subject: Re: avro object reuse From: Tatu Saloranta To: user@avro.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Jun 1, 2011 at 5:45 PM, Scott Carey wrote= : > It would be useful to get a 'jmap -histo:live' report as well, which will > only have items that remain after a full GC. > > However, a high churn of short lived Jackson objects is not expected here > unless the user is reading Json serialized files and not Avro binary. > Avro Data Files only contain binary encoded Avro content. > > It would be surprising to see many Jackson objects here if reading Avro > Data Files, because we expect to use Jackson to parse an Avro schema from > json only once or twice per file. =A0After the schema is parsed, Jackson > shouldn't be used. =A0 A hundred thousand DeserializationConfig instances > means that isn't the case. Right -- it indicates that something (else) is using Jackson; and there will typically be one instance of DeserializationConfig for each data-binding call (ObjectMapper.readValue()), as a read-only copy is made for operation. ... or if something is reading schema that many times, that sounds like a problem in itself. -+ Tatu +-