Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 2322 invoked from network); 9 Mar 2009 17:20:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Mar 2009 17:20:32 -0000 Received: (qmail 33571 invoked by uid 500); 9 Mar 2009 17:20:30 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 33559 invoked by uid 500); 9 Mar 2009 17:20:30 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 33548 invoked by uid 99); 9 Mar 2009 17:20:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 10:20:30 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com designates 209.85.220.158 as permitted sender) Received: from [209.85.220.158] (HELO mail-fx0-f158.google.com) (209.85.220.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 17:20:23 +0000 Received: by fxm2 with SMTP id 2so1229971fxm.43 for ; Mon, 09 Mar 2009 10:20:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=4tUOacA/m2hJPkvaYqF+j0dW7Iur7qbxDhu9R5tBzUc=; b=rObyI7rnr1lkl8MAqHRFeSPTYBF8iwicL98uuaox02skvGXoaGTFc8EDAKo8MircHr nRjQzIu1tMwHZStNQ/zAkGYMV9Eu1cSn9KgrPodRJCueuvxOtNp7DftgUb5hyvO1FBL7 e9P+/XDFZrNwEmdITF4XnsYLnVAcValCynzFY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=kejVLNL0vmK9cb9stnywV1J1lhns4FkGMwj8tPUCmjyVRgwYJoPi185gNrXwytryaY J6q5UG2axa5uSlyCJIvTAVXnCAXvXWuE8r7ic4a0g2K33mpyCjcvMc4AtruxAIygTGai ThK+Mi8diwxoDe9130duCwqWKxLl3kD3Ewwqc= MIME-Version: 1.0 Received: by 10.181.208.11 with SMTP id k11mr2117439bkq.19.1236619202025; Mon, 09 Mar 2009 10:20:02 -0700 (PDT) In-Reply-To: <8f70390903091002p16fbb1e4ied2479c1c8d9100@mail.gmail.com> References: <8f70390903090936q431b6588qf3e227666862d338@mail.gmail.com> <91f3b2650903090940p4b5e5aeft9aced415142e0e9a@mail.gmail.com> <8f70390903091002p16fbb1e4ied2479c1c8d9100@mail.gmail.com> Date: Mon, 9 Mar 2009 18:20:01 +0100 Message-ID: <510143ac0903091020r3d69e9fbp2547ff6a76724dfa@mail.gmail.com> Subject: Re: Datastore and garbage collection From: Jukka Zitting To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Mon, Mar 9, 2009 at 6:02 PM, Paco Avila wrote: > The real question should be "Do I need to call the garbage collection in my > app" ? :P > > And the answer seems to be "YES"! Well, it depends. If your usage patterns permit, you could also just ignore garbage collection entirely. If you don't have lots of short-lived files (or binary properties) in the repository, then the cost of keeping some extra unused binaries in the data store may well be smaller than the cost of getting rid of them. It's worth estimating the rate at which you remove binary data from the repository, and using the result to calculate the best garbage collection intervals. The low (and declining) cost of storage and the typical usage patterns of many content applications (especially ones with versioning) may well suggest that the most economic alternative is to never run the garbage collector. BR, Jukka Zitting