From dev-return-7908-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Apr 23 22:14:47 2008 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 27665 invoked from network); 23 Apr 2008 22:14:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Apr 2008 22:14:46 -0000 Received: (qmail 38696 invoked by uid 500); 23 Apr 2008 22:14:48 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 38670 invoked by uid 500); 23 Apr 2008 22:14:48 -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 38659 invoked by uid 99); 23 Apr 2008 22:14:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 15:14:48 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 22:14:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 897D2234C0FD for ; Wed, 23 Apr 2008 15:11:21 -0700 (PDT) Message-ID: <694924347.1208988681548.JavaMail.jira@brutus> Date: Wed, 23 Apr 2008 15:11:21 -0700 (PDT) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Commented: (OPENJPA-407) Cache SQL (or closer precursors to SQL) more aggressively In-Reply-To: <26454308.1192643510624.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/OPENJPA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591820#action_12591820 ] Kevin Sutter commented on OPENJPA-407: -------------------------------------- Although the previously posted patch helped with performance on an individual EM basis, that was not sufficient when we pushed it through more scalable tests. So, the patch has been re-worked to cache across EMs. The basic concept is the same, but now the cache is longer lived and provides scalable performance improvements. As soon as the testcases and doc updates are done, the new patch will be posted for comments. Hopefully, this version can be committed in the near future. Thanks, Kevin > Cache SQL (or closer precursors to SQL) more aggressively > --------------------------------------------------------- > > Key: OPENJPA-407 > URL: https://issues.apache.org/jira/browse/OPENJPA-407 > Project: OpenJPA > Issue Type: Improvement > Components: jdbc, kernel, query, sql > Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0 > Reporter: Patrick Linskey > Fix For: 1.1.0 > > Attachments: findBy.patch, OPENJPA-407.patch, OPENJPA-407.patch > > > When data is not available in the data cache, OpenJPA dynamically creates SQL to look up the requested data. OpenJPA should more aggressively cache this SQL to accelerate pathways from a cache miss to the database. > The generated SQL takes a number of factors into account, including the requested records, transaction status, currently-loaded data, and the current fetch configuration. Any caching would need to account for these factors as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.