A Look At Microsoft's 'Mini Internet' For Testing IE
MrSeb writes "With the grandiose bluster that only an aging juggernaut can pull off, Microsoft has detailed the Internet Explorer Performance Lab and its extraordinary efforts to ensure IE9 is competitive and IE10 is the fastest browser in the world. Here are a few bullet points: 128 test computers, 20,000 tests per day, over 850 metrics analyzed, 480GB of runtime data per day, and a granularity of just 100 nanoseconds. The data is reported to 11 server-class (16-core, 16GB of RAM) computers, and the data is stored on a 24-core, 64GB SQL server. The 'mini internet' has content servers, DNS servers, and network emulators (to model various different latencies, throughputs, packet loss)."
Why not just use the real internet?
Beaten by Chrome and Firefox.
I couldn't resist. But with all the work and effort and resources going into this, how is it that operations a tiny fraction of this can generate fast, reliable and standards complaint browsers better than MSIE?
Microsoft, the problem isn't that you're not spending enough money. It's that you're not doing it right.
It means that each millisecond of ping is divided into over 9000 parts.
Granularity of 100 nanoseconds: What does that mean?
That's as small as they could get the bits, pounding on them with Steve's chair.
A feeling of having made the same mistake before: Deja Foobar
And still unable to correctly implement CSS2 and HTML4
Fixed that for ya.
Wasn't this a plot-point in the Hitch-Hiker's Guide to the Galaxy series? Having an artificial universe on-site so they could go exploring but still be able to come back for long lunches...
Correctly according to whom? Neither CSS3 nor HTML5 are completed standards and various portions remain in flux. Of the more mature bits IE9 and IE10 implement quite a bit of it and do so quite comprehensively.
MS is also one of very few organizations that is very actively involved with the W3C Test Suite by submitting test cases for each portion of the standard under various circumstances to demonstrate correct behaviors. What Google and Mozilla do instead is slap together a partial implementation and call it a day. More than once has their implementations been found to be not only incomplete but also incorrect.
Stop relying on scores given by non-authoritative tests demonstrating exceedingly limited and selective interpretations of non-standardized functionality. Oh, and HTML5 Video does NOT specify a codec, in fact it was designed to handle many simultaneous codecs, including h.264, which is explicitly referenced in the draft.
Does that mean they have only porn sites with midget porn? And a mini 4chan, populated with toddlers?
What we really need is another Bitcoin story!
Check out my world simulator thingy.
It means the runtime data they have collected is stored in a 100ns interval.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
While slashdot mocks the computer industry marketing for describing computers using a single metric, you seem to be quite happy with that when it comes to browser performance.
An example: Chrome (v8 engine) has this reputation for amazing speed, but IE9 absolutely grinds Chrome into the dust when it comes to simply repositioning elements on screen; something which today's web apps spend a lot of their time doing. You can feel it too if you know what you're looking for. I don't follow IEs development as closely as Chrome or Firefox, but IE must be hardware accelerating these translations.
I fully expect Google to focus on performance cases which help their specific apps. Again, a conflict of interest, akin to Microsoft pre-caching masses of junk, so that Office can appear to start up much faster than the competition.
MSDN blogs are often very technically detailed, written by people who know this stuff from the inside, and if it's about a topic that's of general computing interest then it seems that's a good thing. And the blog in question is chock full of some really good detailed stuff about how they're doing performance testing, reasons why the lab is architected the way it is, detailed graphics on how they measure performance, how they analyze it...on and on.
Frankly, this seems more akin to old Slashdot than a lot of the nonsense we see here today. (That story the other day about a girl sent home from school because her lunch wasn't healthy, and then quickly called into question over what happened? Really? What was that topic even doing on Slashdot in the first place?) Whatever you think about Microsoft, having this extremely detailed look into how one of the world's biggest software vendors (or are they the biggest now?) goes about performance testing, and how they ensure consistent results, should be really, really interesting to anyone involved in IT.
No, it means that Windows has a 100ns granularity on it's timestamps.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms724284(v=vs.85).aspx