RE: [Webtest] memory allocation

[Dierk Koenig]

Really odd numbers.

 

Things that cross my mind:

- very slow server ?

- any location on a mapped/encrypted/compressed drive ?

- Virusscan/Google Desktop or else slowing down file access ?

- multiple taskdefs throughout the tests ?

 

cheers

Mittie

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Luiz Fernando Rodrigues
Sent: Dienstag, 20. Juni 2006 20:25
To: webtest@lists.canoo.com
Subject: Re: [Webtest] memory allocation

Hi Mittie,

  It executes 384 steps in 84 webtests tags. I realised that my tests were not logging out. After modifying it to logout it's a little bit faster: 7 minutes ;-) But it should be done in about 2 minutes, isn't it?
  It's the first time I'm using webtest and I'm using it through appfuse. The test-report tag only generates the reports for the j-unit testing, do you know how do I generate the reports for the web-tests?

Thanks,
Luiz
 

2006/6/19, Luiz Fernando Rodrigues <[EMAIL PROTECTED]>:

Hi,

 

  It's consuming about 500MB and its taking about 10 minutes to execute. I don't have my xml file right now, but tomorrow morning I'll answer how many steps I'm using. Usually the steps are becoming slowly as the script is executed.

 

cheers,

Luiz

 

2006/6/17, Dierk Koenig <[EMAIL PROTECTED]>:

Hi Luiz,

 

welcome to Canoo WebTest.

 

How much MBs of memory is that? How many tests (steps) do you have? How long do they take to execute?

Looking at the generated reports, which steps have an usual long 'duration'?

 

With a quickly responding server, Canoo WebTest executes about 200 server roundtrips per minute, see

http://webtest.canoo.com/webtest/reports/selftest/WebTestReport.html

 

cheers

Mittie

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Luiz Fernando Rodrigues
Sent: Freitag, 16. Juni 2006 23:23
To: webtest@lists.canoo.com
Subject: [Webtest] memory allocation

Hello,

  I'm using canoo webtest in my application and it's taking a lot of time to execute. The problem is that the test allocates several MB of memory slowing the execution. Why does the tests has to allocate so much memory? Is there somehow to flush this allocated memory to make the execution faster?

Thanks,
Luiz