Profiling JavaScript With Ajax View Tool: Spot Poor Performance Client Script In No Time

Ever wondered why your application unreasonably slow? You have it all - most powerful hardware, your database is tuned, SQL queries are optimized, network is barely utilized, and .Net code is super efficient. So why on earth response time is so slow?

The answer might lie in recently developing area – client script. I’ve witnessed few over-AJAX’ed applications with poor performance and far from the best user experience. Quite the contrary what AJAX and other client script flavors are for…

In this post I will show how Ajax View – JavaScript profiler project from Microsoft Research – helped me to spot client side script bottlenecks in no time and make the customer happy.

  • Ajax View – the tool. Ajax View is available for download here. The tool's goal:

"The goal of the Ajax View project is to improve developer's visibility into and control over their web applications' behaviors on end-user's desktops."

Issue Recommendation
1200 lines of inline JavaScript Make JavaScript and CSS External
Using XmlHttp object with its async property set to true while performing time consuming call to the server Do not re-invent the wheel, use ready to-go, proven AJAX Libraries like ASP.NET AJAX
Manipulating large XML islands inefficiently Do not use large XML documents - neither client side nor server side. Use lazy approach of downloading the data on demand.

My related posts

Comments (3)
  1. How to anticipate or better off avoid performance related "surprises" during load and stress

  2. How to anticipate or better off avoid performance related "surprises" during load and stress

  3. Alik Levin's says:

    Field experience proves – the earlier performance is tackled in development lifecycle the better results

Comments are closed.

Skip to main content