Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 83017 invoked from network); 11 Mar 2010 09:11:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Mar 2010 09:11:46 -0000 Received: (qmail 64046 invoked by uid 500); 11 Mar 2010 09:11:13 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 63955 invoked by uid 500); 11 Mar 2010 09:11:10 -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 63948 invoked by uid 99); 11 Mar 2010 09:11:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Mar 2010 09:11:10 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.126.186] (HELO moutng.kundenserver.de) (212.227.126.186) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Mar 2010 09:11:01 +0000 Received: from [10.18.12.56] (host81-137-29-193.in-addr.btopenworld.com [81.137.29.193]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0LyyIe-1NcKau04OG-014GK2; Thu, 11 Mar 2010 10:10:40 +0100 Message-ID: <4B98B38E.9070000@emnico.com> Date: Thu, 11 Mar 2010 09:10:38 +0000 From: Jon Pearson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3 MIME-Version: 1.0 To: derby-user@db.apache.org Subject: Re: Derby Maintenance Activities References: <4B8678F1.7080709@emnico.com> <4B8B9978.2060808@emnico.com> <4B97C050.8080808@emnico.com> <4B97CE34.3000203@gmail.com> In-Reply-To: <4B97CE34.3000203@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+X9sTGX5Wgp2lu6gVwjp3CoXkbIGP7x9Prq6S l6upr9H/cfoQDLpIFR57AXgmgSTNGP3PsQHfHBpnsw1R9P05is nLqljSr9hi4hs3YMk7NBg== X-Virus-Checked: Checked by ClamAV on apache.org Hi Bryan, thanks for responding :-) Certainly we have a lot of churn in 2 tables due to periodic updates which requires the compression. We find that performance drops significantly (x10) around 1.5 months and running the full compression, which rebuilds the indexes, makes a dramatic improvement in performance. We did try to run the compression online but found that some existing compiled statements retained a reference to pages in the pre-compressed table resulting in exception whenever they were excecuted. Since then we have had to perform the compression offline resulting in downtime. Jon On 10/03/2010 16:52, Bryan Pendleton wrote: >> Does anybody have experience of running statistics or compression >> which they can share? > > In my production Derby app, which has run 24x7 for over 4 years, I have > a few tables which I need to compress, approximately every 6 months. > > I have not found it necessary to update statistics on my tables. > > However, my tables are small and don't change very rapidly, which > is I think the primary reason that I don't need to compress them or > recompute their statistics very often. > > I think that if you have highly volatile tables, the need for compression > and statistics is more substantial. > > I think you should set up a mechanism to monitor the performance of your > most important transactions, and you should keep an eye on it, and you > should also periodically run SYSCS_DIAG.SYSCS_SPACE_TABLE, etc., and keep > an eye on those values, and, over time, you will probably develop an > intuition about what level of performance degration justifies doing a > statistics or compression pass. > > thanks, > > bryan > -- Emnico Services Limited, Dauntsey House, Stonehill Green, Westlea, Swindon SN5 7HB Company No. 06390113 This message is confidential and may contain privileged information. If you are not the addressee indicated in this message (or responsible for delivery of the message to them), you may not copy or deliver this message to anyone or take any action in reliance on it. If you have received this e-mail in error, please delete it and notify the sender as soon as possible. The Emnico group of companies do not accept any liability for any harm that may be caused to the recipient's system or data by this message. Please carry out virus and other such checks as you consider appropriate.