From derby-dev-return-93279-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Wed Feb 15 19:01:04 2012 Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C29E29622 for ; Wed, 15 Feb 2012 19:01:04 +0000 (UTC) Received: (qmail 68989 invoked by uid 500); 15 Feb 2012 19:01:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 68965 invoked by uid 500); 15 Feb 2012 19:01:04 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 68958 invoked by uid 99); 15 Feb 2012 19:01:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2012 19:01:04 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [216.32.180.16] (HELO VA3EHSOBE010.bigfish.com) (216.32.180.16) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2012 19:00:55 +0000 Received: from mail195-va3-R.bigfish.com (10.7.14.242) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.22; Wed, 15 Feb 2012 19:00:34 +0000 Received: from mail195-va3 (localhost [127.0.0.1]) by mail195-va3-R.bigfish.com (Postfix) with ESMTP id E183A2400BC for ; Wed, 15 Feb 2012 19:00:33 +0000 (UTC) X-SpamScore: -15 X-BigFish: VPS-15(zzbb2dI9371Ic85fh1447MfecM98dKzz1202hzz8275bh8275dhz2dh2a8h668h839h) X-Forefront-Antispam-Report: CIP:74.62.37.82;KIP:(null);UIP:(null);IPV:NLI;H:CPHUB1.canoga.com;RD:rrcs-74-62-37-82.west.biz.rr.com;EFVD:NLI Received: from mail195-va3 (localhost.localdomain [127.0.0.1]) by mail195-va3 (MessageSwitch) id 1329332431606089_28107; Wed, 15 Feb 2012 19:00:31 +0000 (UTC) Received: from VA3EHSMHS019.bigfish.com (unknown [10.7.14.237]) by mail195-va3.bigfish.com (Postfix) with ESMTP id 8E51422004F for ; Wed, 15 Feb 2012 19:00:31 +0000 (UTC) Received: from CPHUB1.canoga.com (74.62.37.82) by VA3EHSMHS019.bigfish.com (10.7.99.29) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 15 Feb 2012 19:00:31 +0000 Received: from CPHUB2.canoga.com (172.16.1.94) by CPHUB1.canoga.com (172.16.1.93) with Microsoft SMTP Server (TLS) id 8.2.213.0; Wed, 15 Feb 2012 11:01:53 -0800 Received: from vserver1.canoga.com ([169.254.2.24]) by CPHUB2.canoga.com ([172.16.1.94]) with mapi; Wed, 15 Feb 2012 11:01:53 -0800 From: "Bergquist, Brett" To: "derby-dev@db.apache.org" Date: Wed, 15 Feb 2012 11:00:27 -0800 Subject: RE: Quetion on out memory usage Thread-Topic: Quetion on out memory usage Thread-Index: AczsDLjxJ4FlK9m7TpSr+xW5a3F0XgABnQbA Message-ID: <97EB699F861AD841B5908C7CA9C956560206542B1782@VSERVER1.canoga.com> References: <97EB699F861AD841B5908C7CA9C956560206542B173C@VSERVER1.canoga.com> <4F3BE6E3.7050207@sbcglobal.net> <97EB699F861AD841B5908C7CA9C956560206542B1759@VSERVER1.canoga.com> <4F3BF3EB.3040700@sbcglobal.net> In-Reply-To: <4F3BF3EB.3040700@sbcglobal.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-TM-AS-Product-Ver: SMEX-8.0.0.1307-6.500.1024-18710.005 X-TM-AS-Result: No--11.684200-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Content-Type: multipart/alternative; boundary="_000_97EB699F861AD841B5908C7CA9C956560206542B1782VSERVER1can_" MIME-Version: 1.0 X-OriginatorOrg: canoga.com X-Virus-Checked: Checked by ClamAV on apache.org --_000_97EB699F861AD841B5908C7CA9C956560206542B1782VSERVER1can_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable "I am having trouble finding the thread, so perhaps I dreamed all this" I have days like that :) Thanks for your help. Brett From: Katherine Marsden [mailto:kmarsdenderby@sbcglobal.net] Sent: Wednesday, February 15, 2012 1:06 PM To: derby-dev@db.apache.org Subject: Re: Quetion on out memory usage On 2/15/2012 9:41 AM, Bergquist, Brett wrote: Thanks for the reply Kathrine. So in theory however if Derby's estimate w= orks correctly, the sorting should spill to disk and there should be no OOM= errors, right? I was looking for the thread about this but can't find it just now and apol= ogize for being so vague. Perhaps though this will jog someone else's memor= y. As I recall, the scenario that was causing trouble was one where to start = out with there was enough memory for the sort and then during processing o= ther things consumed memory meaning there no longer was room. Having chosen= to go down this path there was no turning back and Derby would run out of = memory on the query. As to whether it "should" spill to disk in that case= I don't know, I think the determination was at least that no one knew how= to do do it. Again, I am having trouble finding the thread, so perhaps I= dreamed all this.... Kathey --_000_97EB699F861AD841B5908C7CA9C956560206542B1782VSERVER1can_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

= I am having trouble finding the thr= ead, so perhaps I dreamed all this”

 

I have days like that J

 

Thanks for your help.

 

Brett

 

From: Katherine= Marsden [mailto:kmarsdenderby@sbcglobal.net]
Sent: Wednesday, F= ebruary 15, 2012 1:06 PM
To: derby-dev@db.apache.org
Subjec= t: Re: Quetion on out memory usage

 

On 2/15/2012 9:= 41 AM, Bergquist, Brett wrote:

Thanks for the reply Kathrine.   So in theo= ry however if Derby’s estimate works correctly, the sorting should sp= ill to disk and there should be no OOM errors, right?

=

 =


I was looking for the thread about this but can't = find it just now and apologize for being so vague. Perhaps though this will= jog someone else's memory.

 As I recall, the scenario that was= causing trouble was one where to start out with there was enough memory fo= r the sort  and then during processing other things consumed memory me= aning there no longer was room. Having chosen to go down this path there wa= s no turning back and Derby would run out of memory on the query.  As = to whether it "should"  spill to disk in that case I don't k= now, I think the determination was  at least that no one knew how to d= o do it.   Again, I am having trouble finding the thread, so perhaps I= dreamed all this....

Kathey


 

= = --_000_97EB699F861AD841B5908C7CA9C956560206542B1782VSERVER1can_--