https://bz.apache.org/bugzilla/show_bug.cgi?id=66248

--- Comment #6 from Vladimir Sitnikov <sitnikov.vladi...@gmail.com> ---
Well, historically, JMeter thread corresponds to a "user session", so
per-thread caching is probably not that far from what typical applications
would have.

For instance, if you fully close web browser, and then open it again, I guess
the very first request would be slower than the second one.
I'm not sure how good JMeter emulates "opening a fresh browser window" when you
"start test".

Just in case:
1) I do not think removing "SSL cache" is an option, since it is expected that
good apps would use SSL session caching.
2) I do not think invalidating SSL cache on each iteration is good (same
reasons as in 1)
3) I do not think caching SSL forever and moving the initialization out of the
measurement loop is good either: if real app executes just one request, they
would face the same SSL startup cost.

Frankly speaking, I have no clear answer how to approach all this, however, I
could imagine:

a) Adding an option like "poorman's warmup" where JMeter discards a couple of
first iterations if there's more than one measurement. For instance, if there
are two or three measurements, then JMeter could exclude the first (or two)
from the report stats

b) Adding something like "exclude first N seconds" or "exclude first N%" when
computing the stats. This should let JMeter and the system under test to warm
up a bit. However, in my experience, there were cases when 30min warmup load
was needed.

c) Adding something like "session management" where different threads could use
the same session. For instance, like in a real application, there might be a
shared "database connection pool", and app threads use the connections from the
pool. The same might be workable for JMeter as well: there might be "HTTPS
connection pool to the system under test", and JMeter threads could use it to
send requests like the typical app would do using HttpClients.

WDYT?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to