Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Gerhard Froehlich" <g-froehlich@gmx.de>
To: <cocoon-dev@xml.apache.org>
Subject: AW: AW: IT'S TIME TO REDO YOUR TESTS, GENTLEMEN!
Date: Fri, 24 Aug 2001 00:38:49 +0200
Message-ID: <LDEKKGCNJLEPFDOEIHFDIEBFCFAA.g-froehlich@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3B850080.72525403@apache.org>
Importance: Normal

>I have created and Active Monitor class that would help us 
>minimize the number
>of accesses to the webapp resources.  Using the FileResource, we 
>can register
>and class (i.e. the cache, etc.) with a PropertyChangeListener.  
>That listener
>will recieve messages who's name is the same as the resource being 
>monitored.
>This effectively eliminates our need to call 
>${file}.lastModified() directly from
>our code.  Each resource in the collection of resources is tested 
>on a frequency
>you specify (i.e. 1/minute, 1/half-hour, etc.).  That way during 
>extreme load
>conditions the number of times we call the "lastModified" method 
>doesn't change.
>Instead of 1/request (with 200 simultaneous users requesting 4 
>pages a second
>that comes to 800 calls a second) it is once per period of time.  
>Even at one
>second, you have called "lastModified" 1/800th of the time using 
>the afforementioned
>example.  It defaults to once per minute which is 1/24000th of the 
>time (that
>is 2400000% decrease in calls.
>
>The Monitor class is in Excalibur's scratchpad section--awaiting 
>the soon inclusion
>in the main excalibur jar.
Sounds very cool. But when you have many resources isn't it dangerous
that this collection becomes to big?

Cheers
Gerhard

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org