Skip to content

CMS performance testing. Part II (DotNetNuke)

February 11, 2011

In this post I’m describing performance review for DotNetNuke CMS.

CMS performance testing. Part I

1. DotNetNuke CMS test results

1.1. Blog page

1.1.1. Summary

Load behavior: Start 100 user simultaneously

Maximum running virtual users: 100

1.1.2. Average values

Blog page, 1 Vuser Blog page, 100 Vuser
Response Time 0.5 14
Processor Queue Length, MS IIS 0.16 7 Not more than 2 for each processor unit
Processor Time (%),  MS ISS 28.6 94 Not more than 85%
Processor Queue Length, SQL Server 0.9 0.9 Not more than 2 for each processor unit
Processor Time (%), SQL Server 28.1 20 Not more than 85%
Disk Time (%),SQL Server 25.06 2.5
Disk Queue Length, SQL Server 0.22

1.1.3. Counters comparison graph

1.1.4.     Results

Here we can see the same situation as it were in 2 previous cases – possible MS ISS CPU bottleneck.

1.2.         Blog post comment (ramp-up)

1.2.1.     Summary

Load behavior: Start 50 every 1 min 30 sec

Maximum running virtual users: 650

1.2.2.     Counters comparison graph

1.2.3. Results

According to this graph we can suppose that .NET Nuke CMS can handle 650 vusers with this system configuration.

1.3.         Blog post comment (flat)

1.3.1.     Summary

Load behavior: Start 100 user simultaneously

Maximum running virtual users: 100 (to have proper numbers to compare with other CMS’s)

1.3.2.     Average values

Blog post comments, 1 Vuser Blog post comments, 100 Vuser
Response Time 0.63 14
Processor Queue Length, MS IIS 0.24 4 Not more than 2 for each processor unit
Processor Time (%),  MS ISS 28.5 88 Not more than 85%
Processor Queue Length, SQL Server 0.44 1 Not more than 2 for each processor unit
Processor Time (%), SQL Server 24.2 27 Not more than 85%
Disk Time (%),SQL Server 6
Disk Queue Length, SQL Server 1.96

1.3.3.     Counters comparison graph

1.3.4.     Results

Also like in previous case here we can see high MS ISS CPU utilization.

1.4.         Data base trace

1.4.1.     Blog page (1 user)

Actually here is the same situation. There were 33 queries and 0 inline ones.

SQL Server execution time:  ≈ 0.5 sec!

1.4.2. Blog post comment (1 user)

According to trace table there were 145 queries. Also there were 0 inline queries. All needed data are executed using stored procedures.

SQL Server execution time:  ≈ 0.5 sec!

In the next post I am going to publish Sitefinity CMS performance overview.

Advertisements
4 Comments
  1. Vasily,

    I like the articles here and the level of research you are doing.

    If you are interested in writing about using Grinder (an open source performance testing tool) to use in the Amazon Cloud for load testing CMS or other Open Source applications I would be interested in publishing your work on sqa.net or software-testing.net. Let me know if this interests you, my sites get approx. 25,000 SQA related visitors a month. Just email me; the email is at the bottom of the http://www.sqa.net home page.

  2. Firstly I need to finish to write this articles 🙂 Then to start a new project and hope to make some research about Grinder tool 🙂

Trackbacks & Pingbacks

  1. CMS performance testing. Part III (Kentico) « QA Questions
  2. CMS performance testing. Part IV (Sitefinity ) « QA Questions

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: