jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herbener, Martin - Division of Engineering and Management" <martin.herbe...@education.ky.gov>
Subject RE: HTTP Cache Manager attributes
Date Wed, 29 Oct 2014 13:08:15 GMT
Philippe,

Thanks very much for the clarification.

Is there anything to monitor to see if items are getting ejected from cache by the LRU algorithm?

Martin

-----Original Message-----
From: Philippe Mouawad [mailto:philippe.mouawad@gmail.com] 
Sent: Tuesday, October 28, 2014 3:47 PM
To: JMeter Users List
Subject: Re: HTTP Cache Manager attributes

Hello,
The HTTP Cache Manager is used to add caching functionality to HTTP requests within its scope
to simulate browser cache feature.
Each Virtual User thread has its own Cache. By default, Cache Manager will store up to 5000
items in cache per Virtual User thread, using LRU algorithm.
Use property "maxSize" to modify this value. Note that the more you increase this value the
more HTTP Cache Manager will consume memory, so be sure to adapt -Xmx option accordingly.

Regards
Philippe M.
@philmdot.

On Tue, Oct 28, 2014 at 4:04 PM, Herbener, Martin - Division of Engineering and Management
<martin.herbener@education.ky.gov> wrote:

> Hi,
>
> When using the HTTP Cache Manager in jmeter 2.11, does the attribute 
> "Max number of elements per cache" mean per-thread, or for the entire 
> thread group, or even the entire plan?
>
> Thanks!
>
> Martin
>
>
> Martin Herbener
> Kentucky Department of Education
> 502 564 2020
>
> KDE on Facebook: www.facebook.com/kydeptofed< 
> http://www.facebook.com/kydeptofed>
> KDE on Twitter: twitter.com/KyDeptofEd
>
>


--
Cordialement.
Philippe Mouawad.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org


Mime
View raw message