Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Vadim Gritsenko" <vgritsenko@hns.com>
To: <cocoon-dev@xml.apache.org>
Subject: RE: IT WON'T BREAK!!! (was Re: New Excalibur--Time to redo your
 Cocoon Load Tests)
Date: Thu, 9 Aug 2001 14:11:56 -0400
Message-ID: <NEBBKBNHBMFHDJPKGCOBIEFECOAA.vgritsenko@hns.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <3B72B919.3B7EB7D5@apache.org>

I found a problem:

Cocoon takes all available memory after ~ 500-600 accesses to http://localhost:8080/cocoon/xsp/simple
and Resin crashes:
#
# An EXCEPTION_ACCESS_VIOLATION exception has been detected in native code outside the VM.
# Program counter=0x50397707
#

Clearly, something is wrong with XSP... Some resources are not released.
cocoon.log file does not have any errors.

Berin, 
could you verify this behaviour?

Vadim

> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> Sent: Thursday, August 09, 2001 12:24 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: IT WON'T BREAK!!! (was Re: New Excalibur--Time to redo your Cocoon Load Tests)
> 
> 
> Vadim Gritsenko wrote:
> > 
> > > -----Original Message-----
> > > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > > Sent: Thursday, August 09, 2001 11:23 AM
> > > To: cocoon-dev@xml.apache.org
> > > Subject: IT WON'T BREAK!!! (was Re: New Excalibur--Time to redo your Cocoon Load Tests)
> > >
> > >
> > > Berin Loritsch wrote:
> > > >
> > > > My initial JMeter load tests show no error messages and plenty of reason to smile.
> > > > I simulated 20 users each hitting the server every 300ms.  When the JVM was in
> > > > a garbage collection cycle, the longest response time was 842ms.  During normal
> > > > opperation, responses were between 0ms and 20ms (55% at 0, 40% at 10, 5% at 20)
> > > > with occasional spikes around 100ms.
> > > >
> > > > I am going to up the JMeter load test to allow for 100 simultaneous users just to
> > > > try and break it.
> > >
> > > I ran it with 100 simultaneous users--and the longest processing times were still
> > > less than 1.6 seconds (my magic "it takes too long on the server" time).
> > >
> > > I wasn't satisfied, so I went with 200 simultaneous users.  My longest processing
> > > time was 3.135 seconds with one Resin Server through Apache, on a 750 MHz Athlon
> > > and 256 MB RAM.
> > >
> > 
> > I assume this results are for static resource (/welcome?), how about dynamic resources?
> > (simple sql or esql)?
> 
> I'll let you know in a bit.  in the mean time, run some tests of your own and give some
> feedback.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 

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