This project is read-only.

Xpedite Performance

The underlying goal of Xpedite is to provide fast run-time compression, minification and combination of CSS, JavaScript and Image resources. To ensure Xpedite has little to no impact on the number of requests that may be processed by a web application, all Xpedited resources are cached in memory. As a result, the underlying worker process memory allocation will increase above what would typically be required if Xpedite was not in use. However, by making use of the typically abundant server memory, Xpedite can enable the web server to process far more requests without adding any real load to the server. Please see the results below.

Environment

64-bit Windows 7 Professional Running IIS7
Intel Core 2 Duo E8500 @ 3.16GHz
6GB Ram

Web Site (Un-Xpedited)

Pummeller Results
StressedUnXpedited.png

Performance Results
PerformanceUnXpedited.png

Summary
1 minute 50 seconds required to complete 20,000 requests.
290 milliseconds required to completely server 1 page.
24% average CPU usage

Web Site (Partially-Xpedited)

Pummeller Results
StressedPartiallyXpedited.png

Performance Results
PerformancePartiallyXpedited.png

Summary
1 minute 20 seconds required to complete 20,000 requests.
215 milliseconds required to completely server 1 page.
5% average CPU usage

Important: CPU usage drops dramatically as server side processing is not required to process each CSS and JavaScript resource required by the page

Web Site (Fully-Xpedited)

Pummeller Results
StressedFullyXpedited.png

Performance Results
PerformanceFullyXpedited.png

Summary
50 seconds required to complete 20,000 requests.
125 milliseconds required to completely server 1 page.
40% average CPU usage

Important: CPU usage is approximately 60% more than the un-Xpedited page; however request throughput has increased by 220%

Last edited Oct 16, 2010 at 10:15 PM by CBaxter, version 6

Comments

No comments yet.