Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 29233 invoked from network); 19 Apr 2007 21:23:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Apr 2007 21:23:46 -0000 Received: (qmail 589 invoked by uid 500); 19 Apr 2007 21:23:52 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 545 invoked by uid 500); 19 Apr 2007 21:23:52 -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 533 invoked by uid 99); 19 Apr 2007 21:23:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2007 14:23:51 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of heavenstar@gmail.com designates 66.249.92.170 as permitted sender) Received: from [66.249.92.170] (HELO ug-out-1314.google.com) (66.249.92.170) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2007 14:23:44 -0700 Received: by ug-out-1314.google.com with SMTP id l31so681606ugc for ; Thu, 19 Apr 2007 14:23:23 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:references:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index; b=K55zRODB/YES+6HmyRC640y+LSXAZhf+ragmTHOIRDnxrcVlL15crcADvUI3PKcE9GAHJPgtEYY9gqIxdU6wWmLHTW8aPbcnEbDlswl+KcAdhF1Kl2vtLXHy+1ynEUniuh6LlrK0gCSjk27CfaotiSmdhVuZ228Gr8T5uEm0yrg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:references:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index; b=Fkltg81D2VSgvE+DCPsLG+8ke8NHZabCOJdsZWccvkl8DjLCA9iRveucEVg2aHrRqYHqDKg1yDWkOxucsJ22FPdWP7CtoSJ6Y3wWVZGQrMY0iI0IQ16yw6mKJ6aXFxbb/mtduosdrR3ltS23fnXhao5nbr7IyhOuqgslI41AcHo= Received: by 10.82.158.12 with SMTP id g12mr3653057bue.1177017803286; Thu, 19 Apr 2007 14:23:23 -0700 (PDT) Received: from heavenstarnotebook ( [88.217.19.149]) by mx.google.com with ESMTP id z40sm901703ikz.2007.04.19.14.23.21; Thu, 19 Apr 2007 14:23:22 -0700 (PDT) From: "Yifan Wang" To: References: <4627D222.3030400@amberpoint.com> Subject: re: How to execute DDL and DML statements concurrently? Date: Thu, 19 Apr 2007 23:23:07 +0200 Message-ID: <002b01c782c8$ee3e0320$3a02a8c0@heavenstarnotebook> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4627D222.3030400@amberpoint.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AceCwhFe5WTqKHmySMSuS9EnmZbUhQABZnQw X-Virus-Checked: Checked by ClamAV on apache.org The DDL statements are mostly =A1=B0create=A1=B1 new tables. In the test, it seems that the problems are not depending on different = DDL statements. Do you mean we change the concurrency level in derby dynamically = depending on the statements? Thanks Yifan -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: Bryan Pendleton [mailto:bpendleton@amberpoint.com]=20 =B7=A2=CB=CD=CA=B1=BC=E4: 2007=C4=EA4=D4=C219=C8=D5 22:34 =CA=D5=BC=FE=C8=CB: derby-dev@db.apache.org =D6=F7=CC=E2: Re: How to execute DDL and DML statements concurrently? > We find that Derby will lock the data dictionary for a relative long=20 > time when executes DDL statements, Does it vary based on the DDL statement? Which DDL statements have you tried, and can you measure differing concurrency levels depending on the statement? thanks, bryan