In Part 1 we discussed that an Ajax enabled application will perform better than a traditional web application. In this post we substantiate this claim with some data.
We compare a web application built the traditional way, in ASP.NET 3.0, with the same application built the AJAX way. Both application fetch data from the Northwind database using the same stored procedures. All the stored procedures have a wait period of 1 second to simulate delay.
We use Fiddler and Firebug to monitor the HTTP traffic, and the Web Application Stress Tool to load the sites with concurrent requests, and examine some of the data generated.
You can read the entire document here [http://docs.google.com/Doc?id=dcggqmtv_36c2tjrqg4].
The source code of the example applications, the Fiddler data used in this post, can be found here. The code is in C#, targets the .NET 3.5 Framework and developed using VS2008 SP1. The Northwind database is included in the download, you can either copy it to the App_Data folder of the applications, or attach them to SQL Server 2005. Rememeber to change to the appropriate connection string in the web.config.
Monday, November 10, 2008
A for Ajax, PART 2: Some data to substantiate claims made in Part 1
Labels:
Ajax,
Fiddler,
Web Application Stress Tool
A for Ajax, PART 2: Some data to substantiate claims made in Part 1
2008-11-10T00:09:00+05:30
santanu
Ajax|Fiddler|Web Application Stress Tool|
Subscribe to:
Post Comments (Atom)