Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 7712 invoked from network); 31 Jul 2006 12:10:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 Jul 2006 12:10:35 -0000 Received: (qmail 88256 invoked by uid 500); 31 Jul 2006 12:10:33 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 88171 invoked by uid 500); 31 Jul 2006 12:10:33 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 88160 invoked by uid 99); 31 Jul 2006 12:10:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jul 2006 05:10:33 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [212.85.125.162] (HELO v07528.home.net.pl) (212.85.125.162) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 31 Jul 2006 05:10:31 -0700 Received: from sj163.internetdsl.tpnet.pl (HELO ?192.168.1.62?) (lgawron.mobilebox@home@80.55.87.163) by m029.home.net.pl with SMTP; Mon, 31 Jul 2006 12:10:10 -0000 Message-ID: <44CDF32A.5090103@mobilebox.pl> Date: Mon, 31 Jul 2006 14:10:18 +0200 From: Leszek Gawron User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Continuations consume ram, possible solutions? References: <98e4f1cd0607270712i77e3bc41j6db1bf9c5f4758a@mail.gmail.com> In-Reply-To: <98e4f1cd0607270712i77e3bc41j6db1bf9c5f4758a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Torsten Curdt wrote: > > > IMO the only way to solve this transparently is to more accressively > expire and limit the number of continuations. It would make sense to > come up with a LRU list of continuations per session. This list has a > maximum size that can defined. So the required maximum can is > predictable. Generating more continuations means using free slots or > throwing away the oldest ones in that LRU list. The janitor would > basically only go through the list and expire to free the slots in > that list. Not that easy: current implementation keeps all parents until leaves expire. So basically you end up with almost whole tree "dead" but as long as there is a single "green leaf" you cannot remove anything. -- Leszek Gawron lgawron@mobilebox.pl IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65