Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 91348 invoked from network); 30 Nov 2006 17:51:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Nov 2006 17:51:03 -0000 Received: (qmail 25637 invoked by uid 500); 30 Nov 2006 17:51:11 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 25602 invoked by uid 500); 30 Nov 2006 17:51:11 -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 25590 invoked by uid 99); 30 Nov 2006 17:51:10 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2006 09:51:10 -0800 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 thomaskelderml@gmail.com designates 64.233.182.188 as permitted sender) Received: from [64.233.182.188] (HELO nf-out-0910.google.com) (64.233.182.188) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2006 09:50:59 -0800 Received: by nf-out-0910.google.com with SMTP id x37so3125350nfc for ; Thu, 30 Nov 2006 09:50:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nuA6IYEQFJAqFeso20t1zDQ1CtJZTy+TlKFo7yNGJwEYSbn3Y/6mG5qwWk6NFF2EcLFKF4aDeFZ67QMENPEEeK5L7vWSQ+TFKHzn8h4Baw65cC5paPqCxAZACQAELMDetNBP8i2PXF1SiGrDT9boWtGoia/w9pdgIUQHEMT3A6k= Received: by 10.82.101.3 with SMTP id y3mr870315bub.1164909037642; Thu, 30 Nov 2006 09:50:37 -0800 (PST) Received: by 10.82.167.17 with HTTP; Thu, 30 Nov 2006 09:50:37 -0800 (PST) Message-ID: <903fbcd30611300950t2e6fdf73j13d63f79c0930da6@mail.gmail.com> Date: Thu, 30 Nov 2006 18:50:37 +0100 From: "Thomas Kelder" To: derby-user@db.apache.org Subject: database in jar slower? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hello, I'm running an embedded Derby database in my java application. I want to use one single file for my database (not the directory with seperate files), so I stored it in a jar file and used the derby:jar: protocol in the connection url. However, compared to using the 'non-jarred' database, my select queries are slower (I don't use compression the jar file), is this normal? Thanks for the info! Best wishes, Thomas