Hi
I think one of the factors being missed out is that most HTTP tests are IO
bound, not CPU bound.
Jmeter makes a request and typically the page will take atleast 2-3 seconds
to return, at which time the thread is idle, waiting for the response and
can be swapped out for another thread without mak
On 12/09/2009, Jakub Białek wrote:
> The conclusions that I made based on my tests. Maybe characteristic of
> tests that I've made is totally different from common jmeter usage
> case so I describe my tests:
> - long running tests: 12h-48h, the goal is to check how application
> behaviour on e
On 12/09/2009, alongir wrote:
>
> Are you using JMeter with distributed configuration?
> do you have any delays between requests?
>
> As I mentioned - in the past, I saw a situation when JMeter (In a
> distributed environment) started to loose connections once a certain number
> of thread was
The conclusions that I made based on my tests. Maybe characteristic of
tests that I've made is totally different from common jmeter usage
case so I describe my tests:
- long running tests: 12h-48h, the goal is to check how application
behaviour on extremely high and long time load
- no any delays b
4 matches
Mail list logo
