Return-Path: 
 <dev-return-45490-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 73165 invoked by uid 500); 29 Jul 2003 09:18:31 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 73148 invoked from network); 29 Jul 2003 09:18:30 -0000
Received: from unknown (HELO pulse.betaversion.org) (217.158.110.65)
  by daedalus.apache.org with SMTP; 29 Jul 2003 09:18:30 -0000
Received: (qmail 29453 invoked from network); 29 Jul 2003 09:18:41 -0000
Received: from unknown (HELO apache.org) (stefano@127.0.0.1)
  by pulse.betaversion.org with SMTP; 29 Jul 2003 09:18:41 -0000
Date: Tue, 29 Jul 2003 11:18:43 +0200
Subject: Re: [RT] Adaptive Caching
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Stefano Mazzocchi <stefano@apache.org>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: 
 <1E0CC447E59C974CA5C7160D2A2854EC09839D@SJMEMXMB04.stjude.sjcrh.local>
Message-Id: <A667E974-C1A5-11D7-9329-000393D2CB02@apache.org>
X-Mailer: Apple Mail (2.552)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


On Monday, Jul 28, 2003, at 17:24 Europe/Rome, Hunsberger, Peter wrote:

> Stefano Mazzocchi <stefano@apache.org> wrote:
>
>> NOTE: this is a refactoring of an email I wrote 2 1/2 years
>> ago.
>
> <snip on entire contents/>
>
> Stefano,
>
> had a little more time to read this last week:
>
> Memphis got hit by some 85 mph winds, no power at our house for a week
> yet, but I have a printed copy...
>
> (See
> http://slideshow.gomemphis.com/ 
> slideshow.cfm?type=GOMEMPHIS&ID=stormpics
> &NUM=8 for an idea of what we got hit with; as of writing this slides
> 50, 51, 57 are from just down the block. We had one fence broken, some
> torn up screens, one air conditioner damaged, but amazingly no other
> damage to our house.)
>
> The little reading I fit in between moving tree branches off our
> property  triggered more ancient memories on paging algorithms.   
> Instead
> of trying to dig up my old notes and books I did a Goggle on "paging
> algorithm" and found lots of good references that I think may be of  
> some
> use.  In particular note:
>
> 	http://www.cs.duke.edu/~jsv/Papers/catalog/node93.html
>
> Essentially, you can treat Cocoon as having multiple applications
> (pipelines) producing working sets (SAX streams) and directly apply the
> tons of research done in this area.

I'll look into the concepts. Thanks.

> You do have to introduce the
> concept of "page size", but this can be arbitrarily small or perhaps
> using some (average?) OS page size might be reasonable?
>
> If you do the Google search you'll notice the references to randomized
> paging algorithms.   I didn't chase these very far other than to
> determine that at least one author shows that they can perform as good
> as conventional algorithms but not as good as the theoretical best.

I still don't understand why you consider my approach randomized  
because, IMO, using a random function to simulate (inferentially  
updated) probability of behavior is not equivalent to a random behavior.

--
Stefano.