Skip to main content

Watson computer smoking hot at Jeopardy challenge

Well, the contest isn't over yet, but the outcome looks like a foregone conclusion. After two days, the Watson computer is poised to defeat the two human champions it is playing. The computer’s performance has been impressive, to say the least, and has left the human contestants looking dazed  and confused.
 And who wouldn’t be? The computer was both ruthless & relentless. (There I go, anthromorphising again.)  The two human champions were barely able to answer a question or two as Watson virtually ran the board in the 2nd day of the competition. Watson, which has to generate an answer in real-time, was so successful at beating the human contestants to the punch that it generated speculation about whether the computer had some kind of unfair time advantage from being fed the question electronically. As reported here (thanks, Phillip), according to IBM, Watson actually cedes a slight “reaction time” advantage to the human contestants. Given how successful Watson is in determining the correct answer so quickly, I think it would be more sporting to give the poor, deserving human players an even bigger head start. Hey, give us a break!
After day 1, the computer and one of the contestants were tied, and it looked as if things would get interesting. After Tuesday’s totally one-sided shellacking, though, commentators were reduced to wondering about the few missteps and obvious quirks that the computer did exhibit on occasion. See, for example: http://www.wired.com/epicenter/2011/02/watson-does-well-and-not/, which analyzes the prodigious strengths the program displayed, as well as describing its few weak spots.
I am afraid that the computer is so good at answering Trivia question that the contest isn’t turning into much of a drama. (It is turning into a great promo, though, for the IBM Watson Research lab.)
However, it remains a challenge of mythic proportions, which is very cool. Like John Henry, the steel-driving man vs. a steam-powered machine, or Charlie Chaplin trapped inside the assembly line in “Modern Times.” On Ray Kurzweil’s web site (he is the author of “The Singularity is Near”), I can almost hear the champagne glasses clinking.

Comments

Popular posts from this blog

How Windows performance counters are affected by running under VMware ESX

This post is a prequel to a recent one on correcting the Process(*)\% Processor Time counters on a Windows guest machine.

To assess the overall impact of the VMware virtualization environment on the accuracy of the performance measurements available for Windows guest machines, it is necessary to first understand how VMware affects the clocks and timers that are available on the guest machine. Basically, VMware virtualizes all calls made from the guest OS to hardware-based clock and timer services on the VMware Host. A VMware white paper entitled “Timekeeping in VMware Virtual Machines” contains an extended discussion of the clock and timer distortions that occur in Windows guest machines when there are virtual machine scheduling delays. These clock and timer services distortions, in turn, cause distortion among a considerably large set of Windows performance counters, depending on the specific type of performance counter. (The different types of performance counters are described here

“There’s a lot more to running a starship than answering a lot of fool questions.”

Continuing a series of blog posts on “expert” computer Performance rules, I am reminded of something Captain James T. Kirk, commander of the starship Enterprise, once said in an old Star Trek episode: “There’s a lot more to running a starship than answering a lot of fool questions.” Star Trek, The Original Series. Episode: The Deadly Years. Season 2, Episode 12. See http://tos.trekcore.com/episodes/season2/2x12/captioninglog.txt. For some reason, the idea that the rote application of some set of rules derived by a domain “expert” can suffice in computer performance analysis has great sway. At the risk of beating a dead horse, I want to highlight another example of a performance Rule you are likely to face, and, in the process, discuss why there is a whole lot more to applying it than might be obvious at first glance. There happens to be a lot more to computer performance analysis than the rote evaluation of some set of well-formed performance rules. It ought to be apparent by now that I …

Virtual memory management in VMware: memory ballooning

This is a continuation of a series of blog posts on VMware memory management. The previous post in the series is here.


Ballooning
Ballooning is a complicated topic, so bear with me if this post is much longer than the previous ones in this series.

As described earlier, VMware installs a balloon driver inside the guest OS and signals the driver to begin to “inflate” when it begins to encounter contention for machine memory, defined as the amount of free machine memory available for new guest machine allocation requests dropping below 6%. In the benchmark example I am discussing here, the Memory Usage counter rose to 98% allocation levels and remained there for duration of the test while all four virtual guest machines were active.

Figure 7, which shows the guest machine Memory Granted counter for each guest, with an overlay showing the value of the Memory State counter reported at the end of each one-minute measurement interval, should help to clarify the state of VMware memory-managemen…