Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

In the TrueLog Explorer statistics tab, what is the difference between "Conditional cache hit" and "full cache hits" against an image file?

In the TrueLog Explorer statistics tab, what is the difference between "Conditional cache hit" and "full cache hits" against an image file?

Cache-hit behaviour on files is dictated by a virtual user"s replay behaviour, determined via:

ACTIVE PROFILE | REPLAY | WEB | "Emulation" and "Simulation" tab settings

A "Full cache hit" denotes that the vuser has automatically used a cached copy of that image, without checking against the server for a newer version.

A "Conditional cache hit" denotes that the vuser has checked against the server for a newer copy of requested image.

If you view the True Log, the key lies in the out-header API requests... an "If-modified-since" conditional check request will be sent by the client to the server will result in a "Conditional cache hit".

You can emulate these scenarios by recording a script against the www.borland.com homepage. Be sure to clear your browser cache before doing this.

1. To generate a "conditional cache hit": before performing a Try Script, set your Active Profile settings to the following:

a. Replay | Web | Simulation: uncheck "Simulate user Behaviour for each Transaction";

b. Replay | Web | Emulation | Document Cache and History: check "Document cache" checkbox and select the "Every Time" radio button.

Set your TMain to be executed twice. On the first TMain execution, image-hits will be in Truelog Explorer"s "Statistics" tab will not report any type of cache hit, as the browser cache is clear. On the second execution of TMain, the image files will be reported as "conditional cache hits", as cache-checking has been performed between transactions.

2. To generate a "full cache hit": before performing a Try Script, set your Active Profile settings to the following:

a. Replay | Web | Simulation: uncheck "Simulate user Behaviour for each Transaction";

b. Replay | Web | Emulation | Document Cache and History: check "Document cache" checkboxand select the "Once per session" radio button.

Set your TMain to be executed twice. On the first TMain execution, image-hits will be in Truelog Explorer"s "Statistics" tab will not report any type of cache hit, as the browser cache is clear. On the second execution of TMain, the image files will be reported as "full cache hits", as no cache checking has been performed between transactions.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:36
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.