Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 73276 invoked from network); 11 Oct 2007 16:00:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Oct 2007 16:00:29 -0000 Received: (qmail 53849 invoked by uid 500); 11 Oct 2007 16:00:16 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 53819 invoked by uid 500); 11 Oct 2007 16:00:16 -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 53810 invoked by uid 99); 11 Oct 2007 16:00:16 -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 09:00:16 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kwsutter@gmail.com designates 209.85.146.180 as permitted sender) Received: from [209.85.146.180] (HELO wa-out-1112.google.com) (209.85.146.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2007 16:00:20 +0000 Received: by wa-out-1112.google.com with SMTP id m28so704862wag for ; Thu, 11 Oct 2007 08:59:55 -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:mime-version:content-type; bh=Usr7UktuCtWALF7AnOiiSZfluuEylG157bwQpqCPuxc=; b=oqQt7X8sV6rD3A5urda1BwxpFIp3dZPIv1+RKujIdKRG6Aw+mZZ0hZhnoBtHLX2fJeKiKLsIA8pgVLFgZNIb0vGRfk24q2inYDauvHC4xZJS1MTnkQ2NJL7oI8JRMdosbOH1JWTbOfA3gfbYp5oibBSbilBdTv/VrIq6g/jsljk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=hLGTZvir1Nl4LHYkn+egPRmV1P/dFWGUMB6yHUiA3A+AblXZV2HfyU9N4cK3qNhknR1vK3pk06R72ySsOPjZTDdVeD3zgNizw+Ur1f8bFNMAiQlHmVZ7NIdZfEKjgtjn5A40ysNnydw8FXJ8yN6pmdBizMcN5SbiSF+HKcH9J1Y= Received: by 10.115.95.1 with SMTP id x1mr2335069wal.1192118395813; Thu, 11 Oct 2007 08:59:55 -0700 (PDT) Received: by 10.114.75.15 with HTTP; Thu, 11 Oct 2007 08:59:55 -0700 (PDT) Message-ID: <89c0c52c0710110859o30d723acocfe5aea142f059bd@mail.gmail.com> Date: Thu, 11 Oct 2007 10:59:55 -0500 From: "Kevin Sutter" To: dev@openjpa.apache.org Subject: Question: Application of QueryCompilationCache for find() and lazy relationships? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17856_24893458.1192118395815" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_17856_24893458.1192118395815 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_17856_24893458.1192118395815--