In the immortal words of Peter Lin ([EMAIL PROTECTED]):
> just for clarification. is you're intent to simulate
>
> 1. requests per second
> 2. concurrent users
> 3. concurrent requests
All three, but with the emphasis on #2.
The testplan is:
Thread Group: 100, 200 or 300 threads, 60-second rampup, 5 loops
|
+---> cookie manager (clear cookies each iteration)
|
+---> random controller
| |
| +---> server1 recording controller
| | |
| | +---> http request (homepage)
| | +---> http request (login)
| | +---> http request (article)
| | +---> http request (article)
| | +---> http request (article)
| | +---> http request (article)
| |
| +---> server2 recording controller (same as s1)
| +---> server3 recording controller (same as s1)
|
+---> Gaussian Random Timer (3000ms dev, 5000ms offset)
This is a slighly pessimistic expression of our company's normal
readership scenario, where our customers get an email with the day's
headlines all at the same time, log in and scan through a few
articles, and then are quiescent until the next email goes out.
(We have to use the random controller because our servers are balanced
with a simple dns roundrobin -- if we let jmeter believe dns, it'll
direct all the threads at the same server.)
> if you're testing pages that are 1k and smaller, than I you will need
> 2 or more jmeter clients running.
Hm, most of our pages are at least 3 or 4k, but can you be a be more
specific as to why this is?
-n
------------------------------------------------------------<[EMAIL PROTECTED]>
"Reading [James] Ellroy can be like deciphering Morse code tapped out by a
pair of barely sentient testicles." (--Dwight Garner, in _Salon_)
<http://blank.org/memory/>----------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
