- JMeter 2.1.1 ... not yet the nighty version.
- Windows XP SP2
- JVM 1.5
its strange that all the times using compression are slower that without using it.
... in the last test i forgot say that i used a static page.
i attached the test plan for any doubt ... but it is very simple ...
greetings, Simon
2006/4/11, sebb <[EMAIL PROTECTED]>:
On 11/04/06, Simon <[EMAIL PROTECTED]> wrote:
> ok, but what do you mean about the clock is running very slowly ... i am
> working in a P4 3.0 ghz with 1g RAM .... do i have to set something to run
> it faster?
The time is calculated by fetching the system time before and after
the sample and taking the difference.
This only produces a non-zero value if the time is updated
sufficiently frequently for it to have changed between the fetches.
A slow-running clock could cause that - but is admittedly not very
likely if your system keeps good time.
Another possible cause is a low update frequency - e.g. if the system
clock (as seen by Java) is only updated every second, it won't in
general be possible to measure elapsed times that are less than a
second.
However, again this is a bit unlikely.
> these are the times returned from the test:
> page with compression ...
>
> 1 /SistemaSimonJSP/JSP/pagina_grande.jsp comprimida 172 true
> 186086
[...]
Where are you getting these figures from? JTL file? Listener GUI? (which?)
They all seem to be rather low.
What version of JMeter? OS? Java?
S.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
