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.

230<br />

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

Figure 6 Scalability results for Logging Application Block<br />

The servers are always CPU bound. Other than the processors, there are no other<br />

dependencies that can cause bottlenecks. The change in memory size between the<br />

2-processor configuration and 4-processor configurations (for both the 32-bit computers<br />

and 64-bit computers) did not affect the relevant measurements.<br />

Here is a summary of the results:<br />

●<br />

●<br />

●<br />

●<br />

The 64-bit computers outperform the 32-bit computers by 45 percent for the<br />

transactions per second measurement and for the total transactions measurement.<br />

For all cases shown in Figure 6, there should be no I/O activity when the % Disk<br />

Time performance counter is less than 7 percent.<br />

The 32-bit computers with 2 processors could not support more than 10 concurrent<br />

users. The 32-bit computers with 4 processors could not support more than 50<br />

concurrent users. The 64-bit computers with 2 processors could not support more<br />

than 10 concurrent users. The 64-bit computers with 4 processors could not<br />

support more than 50 concurrent users. Scalability increases as more concurrent<br />

users are added to the test mix. Scalability increases are greatest when moving<br />

from a 2-processor computer to a 4-processor computer. Moving from a 32-bit<br />

computer to a 64-bit computer yields smaller increases.<br />

The servers’ working sets always require less than 40 MB for all configurations.<br />

The working set of an application is the set of memory pages currently available<br />

in RAM.

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

Saved successfully!

Ooh no, something went wrong!