The .NET CLR Team Tour, Part III

Download this episode

Download Video

Description

Hear the roar!

Oh, that's just the CLR team's lab where they are testing 64-bit versions of the .NET common language runtime. But, first, we drop into Adam Nathan's office where he shows us the pinvoke.net Web site. That concludes our tour of the CLR team, but next week we'll sit down with Jason Zander for an interview about what the CLR team is doing. CLR, by the way, stands for Common Language Runtime.

Tags:

CLR, Jason Zander

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      JasonZ
      That was Scott Wadsworth, SDE/T lead for the JIT/GC/Port team, giving the tour of the lab on the 3rd floor.  It's a pretty impressive setup.

      You should also check out Adam's blog.  In addition to good information on pinvoke.net, he has a lot of good data on MDA's.
    • User profile image
      Charles
      Who said the CLR was a compiler?

      EDIT; Ah. That's stated in the description of the clip. You've got to forgive Scoble. He's not a technical guy Smiley I'll edit it.
    • User profile image
      scobleizer
      Yeah, my bad. Hey, not too shabby to have Larry to clean up my messes, though!
    • User profile image
      staceyw

      huh.  Can't believe all those standup pcs.  Would think nothing but 1Us-2Us rack mounts to keep things simple and tight.  I loved how the guy at the end says that is it and walks away.  Gotta do the next build... Smiley

    • User profile image
      Larry​Osterman

      Edit: Never mind, it's been fixed

    • User profile image
      JasonZ
      staceyw wrote:

      huh.  Can't believe all those standup pcs.  Would think nothing but 1Us-2Us rack mounts to keep things simple and tight.



      There are typically two sources of tower machines in the lab.  The first is new prototype hardware from the vendor where they haven't actually made 1Us-2Us yet (some of the hardware in the lab hasn't hit the street yet).  The second is older models that have outgrown their usefulness as development machines and come out from under the desk and into the lab.  We keep them in the lab to increase our machine mix.  We typically find bugs in instruction scheduling, chip errata, and (since the machines often have less RAM) memory utilization.  Any time we trully recycle old machines, they are replaced with rack mounts.


      staceyw wrote:


      I loved how the guy at the end says that is it and walks away.  Gotta do the next build... Smiley



      We'll have to introduce Alain Rait next time (the Test Lead who owns our BVT lab.  He's a former drill sergeant (no kidding) who keeps our machine utilization up to around 85% across the board.  No slacking <g>

    • User profile image
      rdecarlo73
      Total sidebar here... but it's the Egg Nebula.
    • User profile image
      rhm
      I like the way the camera picked up the speach just fine in the machine room, but out in the corridor afterwards I had to turn up the volume to hear the guy!
    • User profile image
      The Dealman
      what model our those hp servers?

      time mark in video 04:41

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.