- Finding client side performance of a web application in the production environment.
- Making changes or adding instrumentation on client side code at production stage is dangerous.
- HTTP profiling tools do not provide rendering time details.
- Make the web application behavior uniform across different execution environments like IE 6, IE8, FireFox, Chrome, etc, since Array.sort() consumes processor utilization in IE than other browsers and Array.join() takes very less in IE than others.
- Easy and instant deployment
- Dynamic extension (you can add any stuff on the response of a web request)
Thanks to Emre Kiciman and Benjamin Livshits at Microsoft Research for implementing this great tool.
How Does It Works
A component (Transformer) which automatically rewrites the actual code to serve differently instrumented versions.
One or more components (Controller and Log Collector) which should continuously observe the end-to-end application behavior on the client side.
The observed results are then analysed and used to guide the adaptation of the dynamic instrumentation policy (Dynamic Extension Generator).
AjaxView supports the following broad categories of instrumentation policies:
Runtime analysis and debugging
Let us see a practical walk-through on the next post for better understanding of this tool.
Visit http://research.microsoft.com/en-us/projects/ajaxview/ to know about this tool (or platform) and download.
Read the AjaxScope: A Platform for Remotely Monitoring the Client-Side Behavior of Web 2.0 Applications white paper to know in depth about this tool.
To know in depth details of the adaptive and distrubuted instrumentation, read the Live Monitoring: Using Adaptive Instrumentation and Analysis to Debug
and MaintainWeb Applications white paper.