Enterprise Library Test Guide - Willy .Net

184
Enterprise Library Test Guide
●
●
●
●
The number of elements to remove during scavenging was 10.
The cache storage was both in-memory and a SQL Server database.
The cache size was 2, 000 KB.
The number of elements in the cache was between 900 items and 2,000 items.
Table 2 lists the scenarios for the Caching Application Block. Here is an explanation
of each of the columns:
●
●
●
●
ID. This column lists the ID number for each scenario.
Scenario. This column lists the Caching Application Block scenario being tested.
Users. This column lists the different numbers of users that the tests simulated.
Expiration policy. This column lists the different expiration policies that were
used during the tests.
Table 2: Caching Application Block Scenarios
ID Scenario Users Expiration policy
1 Add an item. 1, 10, 50, 150, Never/Absolute/FileDependency/
300
Extended Format
2 Read an item. 1, 10, 50, 150,
300
3 Remove an item. 1, 10, 50, 150,
300
4 Add and remove an item. 1, 10, 50, 150,
300
5 Add and remove and read an
item.
6 Add and remove and read and
flush an item.
7 Flush an item. 1, 5
1, 10, 50, 150,
300
1, 10, 50, 150,
300
Never/Absolute/FileDependency/
Extended Format
Never/Absolute/FileDependency/
Extended Format
Never/Absolute/FileDependency/
Extended Format
Never/Absolute/FileDependency/
Extended Format
Never/Absolute/FileDependency/
Extended Format
Creating a Test Harness
Each iteration of the test should create the CacheManager object so that the cost of
creating the object is included in the performance metrics. In addition, every item in
the cache requires a unique key. For more information, see Generating Unique Keys.
For an example of how to create a test harness, see Building Test Harnesses. This section
also contains an example of a Web page for the Caching Application Block test
harness.
Generating Unique Keys
Every item that is added, read, or removed from the cache requires a unique key.
Another way to think of this is that each thread, which represents a virtual user, requires
its own key. The Caching Application Block test increments the key value until