From dev-return-6422-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Oct 11 17:01:35 2007 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 52649 invoked from network); 11 Oct 2007 17:01:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Oct 2007 17:01:34 -0000 Received: (qmail 80007 invoked by uid 500); 11 Oct 2007 17:01:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 79968 invoked by uid 500); 11 Oct 2007 17:01:22 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 79958 invoked by uid 99); 11 Oct 2007 17:01:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2007 10:01:21 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of plinskey@gmail.com designates 64.233.184.237 as permitted sender) Received: from [64.233.184.237] (HELO wr-out-0506.google.com) (64.233.184.237) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2007 17:01:25 +0000 Received: by wr-out-0506.google.com with SMTP id l58so382554wrl for ; Thu, 11 Oct 2007 10:01:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=wpWxi6BxluKeyPOwq4uFWePXXVeM8B8LnToFLZGarwE=; b=uKjY94vG9DvpSxtad1n1zEb0xBT5WXh3Wu1TPz6nRA77YShMGWIEG7DTkI1+tJgW7roYoUX2W7XCoipZaRuu8bpWs+2MS1Hx58NjtoJYoiukpAwOZmAM4Y84OwyCwB8aCRiBVP/m83QyMkBsLCg2+M4bQ2Ze8Bl+soRHcsEBp7g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CnM2PQo+8dleczA8I7UR3NLwUblF2ryUZv8p53kmzAoRQ6c8BNPEhvdkpYXOd1KzayXSvPjL1OnWJ+lskZHCleeI/L4X7vw5g52cvHTHlsgsFCAQhghbKZ9I1Bcxxv6O8t6q0T64Zt4SrHpDLzpcKY/feRzAjnuoV9nLV5HH/dc= Received: by 10.142.128.6 with SMTP id a6mr704713wfd.1192122063013; Thu, 11 Oct 2007 10:01:03 -0700 (PDT) Received: by 10.143.165.19 with HTTP; Thu, 11 Oct 2007 10:01:02 -0700 (PDT) Message-ID: <7262f25e0710111001k3481d5a3jb87334cdd51f6502@mail.gmail.com> Date: Thu, 11 Oct 2007 10:01:02 -0700 From: "Patrick Linskey" To: dev@openjpa.apache.org Subject: Re: Question: Application of QueryCompilationCache for find() and lazy relationships? In-Reply-To: <89c0c52c0710110859o30d723acocfe5aea142f059bd@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <89c0c52c0710110859o30d723acocfe5aea142f059bd@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org The query compilation cache doesn't cache data that would be directly useful for those calls. However, I'm all for optimizing those pathways, and the query compilation cache could be a place to store whatever intermediate caches we are able to assemble. -Patrick On 10/11/07, Kevin Sutter wrote: > Hi, > For those of you that are more verse with the QueryCompilationCache, I'm > wondering how difficult it would be to utilize this type of cache for the > em.find() operations as well as traversal of lazy relationships. We're > finding that these operations are more prevalent in customer's applications > than the use of createQuery() and createNamedQuery() operations and it's > affecting our performance (especially as compared to our competitors). So, > I am wondering whether anybody has put any thought in this space before I do > a deeper dive. Any suggestions or thoughts? > > Thanks, > Kevin > -- Patrick Linskey 202 669 5907