Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D926E105B2 for ; Sat, 11 Jan 2014 12:55:09 +0000 (UTC) Received: (qmail 89011 invoked by uid 500); 11 Jan 2014 12:52:02 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 88953 invoked by uid 500); 11 Jan 2014 12:51:46 -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 88935 invoked by uid 99); 11 Jan 2014 12:51:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 12:51:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of john.foreign@gmail.com designates 74.125.83.49 as permitted sender) Received: from [74.125.83.49] (HELO mail-ee0-f49.google.com) (74.125.83.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 12:51:33 +0000 Received: by mail-ee0-f49.google.com with SMTP id c41so2310837eek.22 for ; Sat, 11 Jan 2014 04:51:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ApNZqBT1Vut8xXwcTcfh0MsTCLw8APbxRAAaxbl4YO0=; b=XMVne/uSEwBPwS40QKopCnu2Kz+57OTYLIbLinudNnmKYUD5tWrgB+o3wA5jPKpDY9 X0Uo3ZJ3eWoJIXa8bZVMvXLrY3RuUqxtLjNxx1YsO1MAZBq4iDyVoxQPkuwmJsGdbJck +S1NC9dPIh45x1iFt8OtXKEdKtWVZsqXJiEnN3JKVHZD+PKt26ZHAp2mi+RWtcGMaNcn CdEQRmxAiddifgyGgCwygbUac+RjF9JFSt0mqcxFhhzJR64luF57i07XmtCPvKnmQpxT XR0X2lCjqCaHDhFPdfgtsg1zmSbH7Hjmz9KLUGSBY4J+DMQP7Wjm35Lm/yEWn+UOli0Q /p8w== X-Received: by 10.15.82.8 with SMTP id z8mr15969876eey.25.1389444673217; Sat, 11 Jan 2014 04:51:13 -0800 (PST) Received: from [192.168.1.101] (bzq-84-111-131-91.red.bezeqint.net. [84.111.131.91]) by mx.google.com with ESMTPSA id w4sm2403645eef.20.2014.01.11.04.51.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 Jan 2014 04:51:12 -0800 (PST) Message-ID: <52D13E3B.7050406@gmail.com> Date: Sat, 11 Jan 2014 14:51:07 +0200 From: John English User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: derby-user@db.apache.org Subject: Re: Can I run derby for a long time? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 10/01/2014 20:59, Han Xin wrote: > Can I run derby for a long time with many inserts, deletes and updates? Are the > memories, disk spaces recovered after deletion/updating? My experience is similar to Bryan's. I'm running a server on a small cheap Linux box using Jetty and Derby which also has up to about 100 concurrent clients, and I stop it for about half an hour every 3-4 months to install fixes and updates. I've been running it like this for about 3 years now. -- John English