07.11.2014 Views

Enterprise Library Test Guide - Willy .Net

Enterprise Library Test Guide - Willy .Net

Enterprise Library Test Guide - Willy .Net

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

220<br />

<strong>Enterprise</strong> <strong>Library</strong> <strong>Test</strong> <strong>Guide</strong><br />

●<br />

●<br />

●<br />

●<br />

●<br />

The elapsed time spent performing garbage collection since the last garbage<br />

collection recycle should be less than 10 percent during stress and performance<br />

tests.<br />

A Gen 2 collection should be one-tenth the value of the number of Gen 1 collections<br />

and a Gen 1 collection should be one-tenth the value of the number of Gen 0<br />

collections.<br />

Where applicable, there should be no SQL Server deadlocks.<br />

Where applicable, the SQL Server Lock Waits/sec performance counter should be<br />

zero.<br />

Where applicable, there should be no SQL Server exceptions.<br />

Table 26 lists the relevant performance counters and their respective thresholds.<br />

Table 26: Performance Counters Used in Performance and Stress <strong>Test</strong>ing<br />

Area Performance counter name Threshold<br />

Processor % Processor Time This value should be close<br />

to 100 percent when the<br />

load simulation saturates the<br />

application block. This usually<br />

happens with 10 virtual<br />

clients because there are no<br />

think times. Any contention<br />

or external dependency may<br />

cause this value to be too<br />

low. For scalability tests, this<br />

metric is used in conjunction<br />

with end-to-end transactions<br />

per second.<br />

Processor % Privileged Time This value should be no<br />

higher than 20 percent to 25<br />

percent.<br />

Process (w3wp) Handle Count This value should remain<br />

stable during stress tests.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!