- Configuring your browser. AjaxView is running as a proxy (localhost) at port number 8888 so that you should configure your browser to listen from this proxy. Since, this is a proxy tool, you can use any browser. I am using Firefox, because IE is running for this blog post writing.
- Execute AjaxView. AjaxView is running in a console window.
- Enter the URL. Type https://udooz.net/blog.
You can do whatever you want in the site to profile the event you want to capture. You can see the instrumented code based on the performance policy injected into the blog site code. AjaxView injects necessary code for performing profiling, logging an send it to AjaxView at the head of the page.
Whereever required, it injects the profile code like the following
During the loading and other execution of your web application, the above profile codes send the log details back to AjaxView using XMLHttpRequest. See the following figure.
Getting the Results
Enough logging, now let us see the analyzed results of the logs by opening new tab in FireFox and type . This is a fake URL for getting analyzed reports from AjaxView proxy. A two column page will appear. The left side contains the following links:
- JS Performance Statistics
- Proxy Statistics
- LM Policies
- Clear Statistics
Our focus in on JS Performance Statistics.
JS Performance Statistics
- Worst Performance (ms) – Performance of the slowest function in the page.
Comparison with IE Development ToolBar Profiler