That's a start many thanks, but the change proposed wouldn't allow to submit more requests than the web application could handle. If I wanted to send 10 reqs per sec and the response time was more than 1 sec, than I would have to increase the timer to be bigger than 1 sec, and we would still be stuck with in the same problem. Does this make sense?
What I'm looking for is a timer more than a delay. Thanks, Michele -----Original Message----- From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]] Sent: Friday, October 11, 2002 10:50 AM To: JMeter Developers List Subject: Re: delay in timers What you suggest is already filed in an enhancement request in http://issues.apache.org/bugzilla/show_bug.cgi?id=11523 Note the suggestion is to create another type of timer, not to change the current functionality (since users may be relying on it). Programming this should not be difficult. Salut, Jordi. Michele Curioni wrote: > Hi all, > I had a look at the way jmeter manages the timer function, and I found that > it basically delays the request of each thread. > In this way it's not possible to simulate a specific workload to a web > application like > for example submitting the web app with 10 requests per second. > In fact setting the number of threads to 10 and a constant timer of 1000 ms > would not result in 10 requests per second, but just to 10 requests running > in > an indefinable interval, depending on the performance of the web > application. > > Would it be possible to change the code so that the timer set an interval > between two requests > independently from the response time > and not just the interval between the response and the next request? > > Thanks, > Michele > > > > Michele Curioni > Software Engineer > tel: 01256 484815 > fax: 01256 811430 > email: [EMAIL PROTECTED] > www: www.gointeract.tv > GOiNTERACTtv > c/o Sony, Priestley Road, Basingstoke, > Hampshire, RG24 9JP, UK > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
