A small benchmark of Folks performance against ASP.NET Ajax.
Scenario
Population a GridView with a specific number of Person { Name, Email } items.
Configuration
Running on Centrino Duo 1,67, 1GB RAM on Windows XP Pro SP2, Firefox 2 with
Firebug (used to collect the response), IE6 with Fiddler to collect responses' size. The Web Form developed contains a TextBox, a Button and a GridView. The GridView was configured to show 100 records, others only with pagination (what isn't covered here).
Data
The data collected was the response (including client response) in milliseconds and payload for populate a GridView
with 10, 100, 1k, 10k and 100k of items.
Result
The result is shown below (Response Time in milliseconds):
|
Items |
Response (ms) |
Bytes Sent |
Bytes Received |
|
Folks |
ASP.NET Ajax |
Folks |
ASP.NET Ajax |
Folks |
ASP.NET Ajax |
|
10 |
15 |
31 |
1.937 |
1.959 |
4.012 |
4.394 |
|
100 |
32 |
109 |
1.938 |
1.960 |
30.688 |
30.893 |
|
1000 |
31 |
281 |
9.297 |
9.323 |
31.785 |
31.984 |
|
10000 |
46 |
203 |
9.354 |
9.384 |
31.891 |
32.090 |
|
100000 |
140 |
281 |
9.373 |
9.387 |
31.896 |
32.095 |
Conclusion
As a basic benchmark, Folks shown to be faster in all cases. If you have a comparison
idea, please tell us commenting this post.
