Project JSMeter: JavaScript Performance Analysis in the Real World
- Posted: Mar 28, 2010 at 5:03 PM
- 59,849 Views
- 6 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- High Quality WMV (PC, Xbox, MCE)
- MP3 (Audio only)
- MP4 (iPod, Zune HD)
- Mid Quality WMV (Lo-band, Mobile)
In this episode of Expert to Expert (to Expert), Erik Meijer joins MSR research scientists Ben Livshits and Ben Zorn to talk about JavaScript, project JSMeter and today's trends in web programming.
Dr. Zorn and Dr. Livshits have been doing a significant amount of research on how JavaScript is used in the real world by analyzing JS execution on large-scale (JS-heavy) commercial web sites. Their formal exploration of JS executing in the real world, Project JSMeter, has yielded results, which seem to indicate that current JS performance test suites are at best suspect in terms of how JavaScript is actually running on the web, in production, on real sites, etc. But read the findings and make your own judgments, of course.
Tune in. Enjoy.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
I watched this two weeks ago and skimmed the paper. Now I have this question: Have you studied the number of (simultaneous) XmlHttpRequests most web apps make?
I just FW'd it to the two Bens.
C
Thanks for the question. We did not measure the number of simultaneous XmlHttpRequests in our current study, although that's an interesting question. There are a number of additional measures like that including the ways the typical WebApps interact with the DOM that we are also interesting in knowing. While we do not have concrete plans right now for collecting such data, if we do get it, we'll make it available from our project website.
Thank you for your time answering my question.
My question arose when I was reading this proposal to add a priority property to XmlHttpRequests, but I had my doubts whether it would be a useful addition.
There's a blog post about the report: www.belshe.com/2010/03/31/how-to-tune-a-porsche/
I wonder how the authors would respond to that.
Thanks for your question. We are aware of the related blog post and disagree with the conclusions the author reaches. Specifically, the analogy with the elephant, while quite visually provacative, is inaccurate. The implication is that browser users want to drive their browsers on a racetrack all day (e.g., the benchmarks). Browser users want high performance, but not for small benchmarks that don't correspond to their daily experience. A better analogy would be to consider driving your browser down a city street in traffic. In that case, which we argue is the common case, the fact that your browser performs like a Porsche on a racetrack isn't as meaningful. What the user cares about is how it handles in traffic. We are presenting this research at the WebApps 2010 conference in Boston, on June 23, 2010 (http://www.usenix.org/events/webapps10/).
Remove this comment
Remove this thread
close