Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 41708 invoked from network); 29 Jul 2009 13:08:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Jul 2009 13:08:42 -0000 Received: (qmail 22107 invoked by uid 500); 29 Jul 2009 13:08:43 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 22044 invoked by uid 500); 29 Jul 2009 13:08:42 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 22031 invoked by uid 99); 29 Jul 2009 13:08:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2009 13:08:42 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.18.43.132] (HELO sca-es-mail-1.sun.com) (192.18.43.132) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2009 13:08:32 +0000 Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n6TD8Bl8022639 for ; Wed, 29 Jul 2009 06:08:11 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KNJ00C00OG03D00@fe-sfbay-09.sun.com> for derby-user@db.apache.org; Wed, 29 Jul 2009 06:08:11 -0700 (PDT) Received: from richard-hillegas-computer.local ([unknown] [129.150.240.15]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KNJ00MJEOHLZU40@fe-sfbay-09.sun.com> for derby-user@db.apache.org; Wed, 29 Jul 2009 06:08:10 -0700 (PDT) Date: Wed, 29 Jul 2009 06:08:08 -0700 From: Rick Hillegas Subject: Re: Slow performance on 5 or more joins in a star schema In-reply-to: <64A84ACFB244464D8C7086F909034D5401C92086C7@athena.isdwhq.com> Sender: Richard.Hillegas@Sun.COM To: Derby Discussion Message-id: <4A7049B8.8050101@sun.com> References: <64A84ACFB244464D8C7086F909034D5401C92086C7@athena.isdwhq.com> User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) X-Virus-Checked: Checked by ClamAV on apache.org Hi Dustin, As you note, the Derby query optimizer only considers left-deep trees. I have logged an enhancement request for support for bushy query plans: DERBY-4327. If many people vote for this issue, we can consider it for the next Derby feature release. Regards, -Rick Dustin T. Clifford wrote: > > All, > > > > We have implemented a star schema and we are noticing that queries > involving 5 or more joins perform very slowly. We have, also, noticed > that batch updates and deletes perform slowly. We support multiple > databases and, as we improve on performance in SQL Server and Oracle, > we notice a trend in the opposite direction with Derby. > > > > I know that the Derby optimizer use to only consider left-deep > trees. Is this still true or is there another optimizer that we can > use? Does anybody have any advise on working in a manner that can > provide good performance on Derby, SQL Server and Oracle? Any advice > would be appreciated. > > > > *Dustin Clifford* > > >