Hi,
I've configured a test with 100 thread groups (one thread per thread
group) and added a constant throughput timer to get a 10 requests per
second performance. To do so, I configured target throughput to 600
(samples per minute) and selected to compute performance based on all
active threads.
Hi All,
I'm using JMeter 2.0.3 for Load testing.
My test plan contains
1. Login in the user site.
2. Click on the respective PPT.
3. View.
4. Preview.
5. Add Slide to Slide bin of the default tray.
6. Download the Slides.
7. Clear the
Hi,
I'd like to try another way to solve my problem using beanshell sampler
as I can manipulate IsSuccess variable with beanshell.
But as I downloaded the latest jar for beanshell and added it to the
classpath in jmeter GUI, I can't create a script. I tells me that
beanshell interpreter was
Hello!
Sorry that I disturb you again. Can somebody answer my question:
Can I test a WebSphere portal with jmeter?
The portal url's are in the following format:
I'm not sure I understand why you have 100 thread groups.
you can put the requests in sequence in 1 threadGroup and increase the
thread count to 100 with 0 second ramp up.
peter
On 12/9/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
hi!,
I'm using Jmeter to perform a peak test of my web
people have used jmeter to test struts, so it should be feasible. I've never
done it myself, so can't really give you an pointers.
peter
On 12/9/05, Sorin N. Ciolofan [EMAIL PROTECTED] wrote:
Hello!
Sorry that I disturb you again. Can somebody answer my question:
Can I test a WebSphere
El vie, 09-12-2005 a las 15:17, Peter Lin escribió:
I'm not sure I understand why you have 100 thread groups.
you can put the requests in sequence in 1 threadGroup and increase the
thread count to 100 with 0 second ramp up.
peter
Because the requests must be different. If I do what you say,
for what it's worth, it's nearly impossible to get all 100 requests within
500ms. The reason for this is making the initial connection to your
webserver will have a high initial cost. How many iterations are you using.
if you look at all formal performance test specifications, they all have a
First of all, thanks a lot for your answer peter,
I comment it between lines:
El vie, 09-12-2005 a las 16:00, Peter Lin escribió:
for what it's worth, it's nearly impossible to get all 100 requests within
500ms. The reason for this is making the initial connection to your
webserver will have a
your explanation helps, but here's the thing. Say I want to simulate the /.
effect. If 5K people all hit /. at the same exact nanosecond, all the
connections will still be queued up by the server and the webserver will
process them one at a time. As soon as a server thread/precess starts to
Thanks for all your feedback. I am currently working on my own stream
replacement facility.
As far as I understand the JMeter implementation, all the preprocessor
variables are stored in an instance of JMeterVariables which can be accessed by
means of calling
mike or sebb would know more about this area. my knowledge of the variable
stuff is pretty weak
peter
On 12/9/05, Brudermann Roger [EMAIL PROTECTED] wrote:
Thanks for all your feedback. I am currently working on my own stream
replacement facility.
As far as I understand the JMeter
I originally wrote all my scripts using the HTTP Request sampler. Now
there is a second one that is called HTTP Request HTTPClient. What is
the advantage of using one vs the other?
So far the HTTP Request sampler has worked well for my tests except
that the line speed property cannot be used
the advantage of the HTTPClient version is it supports keep alive and slow
connections correctly. the default sun implementation does not and hasn't
since the beginning.
peter
On 12/9/05, Christensen, Alan [EMAIL PROTECTED] wrote:
I originally wrote all my scripts using the HTTP Request
The file
extras/ConvertHTTPSampler.txt
gives instructions on how to convert the samplers.
S.
On 08/12/05, Peter Lin [EMAIL PROTECTED] wrote:
it is the one named HTTPClient. that is correct.
peter
On 12/8/05, Christensen, Alan [EMAIL PROTECTED] wrote:
I'm not sure I know what the Http
I suspect part of the problem is that all the threads start at once,
and having 100 thread groups with only 1 thread in each will make it
tedious to fix - you'll need to add a gradually increasing delay to
each of the thread groups.
What happens if you have fewer thread groups and more threads in
Put the bsh jar in the lib directory, and remove from the classpath.
The classpath seems to be processed a bit too late for BeanShell.
S.
On 09/12/05, Nicolas [EMAIL PROTECTED] wrote:
Hi,
I'd like to try another way to solve my problem using beanshell sampler
as I can manipulate IsSuccess
Are these fixed URLs? Or do they vary?
If fixed, then record a script.
If they vary, they'll need to be extracted from the previous response.
Have a look a the various Pre- and Post- Processors.
S.
On 09/12/05, Peter Lin [EMAIL PROTECTED] wrote:
people have used jmeter to test struts, so it
n 09/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
El vie, 09-12-2005 a las 15:17, Peter Lin escribió:
I'm not sure I understand why you have 100 thread groups.
you can put the requests in sequence in 1 threadGroup and increase the
thread count to 100 with 0 second ramp up.
peter
I understand what you tell me. I think the problem is a set of things:
1.- The server has to queue all the requests. Although it can have
enough threads to handle all of them, only one thread can be in
execution at a given time.
2.- Jmeter has the same problem when launching all the requests.
3.-
Thanks for your comment sebb,
if I have more than one thread in each thread group my problem is
ensuring that each thread launches a different request, because each
thread will send the same sequence of requests under the threadgroup.
I've tried using an interleave controller, but it deals the
I added the method
public Iterator getIterator()
to JMeterVariables a little while ago.
It's in the 2.1 branch and the nightly build.
Another way would be to specify the variables that need replacement,
rather than looking for all possible instances of a variable
reference. That might prove
El vie, 09-12-2005 a las 18:10, sebb escribió:
n 09/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
El vie, 09-12-2005 a las 15:17, Peter Lin escribió:
I'm not sure I understand why you have 100 thread groups.
you can put the requests in sequence in 1 threadGroup and increase the
I believe it also supports NTLM authentication even when running on
non-Windows hosts.
It's a lot more configurable. Adding slow connections to the default
implementation is hard work. The Apache implementation has proper
Cookie handling (though we aren't using that yet). It also has highly
On 09/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
Thanks for your comment sebb,
if I have more than one thread in each thread group my problem is
ensuring that each thread launches a different request, because each
thread will send the same sequence of requests under the threadgroup.
On 09/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
El vie, 09-12-2005 a las 18:10, sebb escribió:
n 09/12/05, Iago Toral Quiroga [EMAIL PROTECTED] wrote:
El vie, 09-12-2005 a las 15:17, Peter Lin escribió:
I'm not sure I understand why you have 100 thread groups.
you can
honestly, I don't understand why first request needs to be different for all
threads. if the point is to measure an application's ability to handle a
sudden spike, it's better to pick a very heavy page and set 1 threadGroup
with 100 threads and hit it.
using different thread groups just means
El vie, 09-12-2005 a las 18:49, Peter Lin escribió:
honestly, I don't understand why first request needs to be different for all
threads. if the point is to measure an application's ability to handle a
sudden spike, it's better to pick a very heavy page and set 1 threadGroup
with 100 threads
thanks for explaining. that makes sense now. given the application is
caching, having different requests would be crucial for valid measurement.
chances are, you'll need to use atleast 4 clients and split the test plan
into 4 smaller test plans. this way, it increases the chances that the
threads
On 09/12/05, Peter Lin [EMAIL PROTECTED] wrote:
thanks for explaining. that makes sense now. given the application is
caching, having different requests would be crucial for valid measurement.
chances are, you'll need to use atleast 4 clients and split the test plan
into 4 smaller test plans.
31 matches
Mail list logo
