Ask a questionAsk a question
 

AnswerOSD Deployment (Multicast vs. Unicast) Network Performance

  • Friday, November 06, 2009 11:02 PMMikeFi Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have setup SCCM R2 SP2 to deliver an OS Image via multicats. Everything works great! The issue is not with operational function but with theoretical.

    It is my understanding the Multicasting will reduce the network load compared to unicast deployments.

    When i ran my OSD via unicast, i hit F8 during the application of the image and ran TASKMGR to view network util. It was on average about 10%.

    When i ran my OSD via multicast, same process except my network util was on average 17%.

    Isn't this backwards? I have also been triggering the CRITICAL interface load (if_load) alerts on our router when deploying with Multicast and NOT EVEN TRIGGERING THE WARNING threshold when deploying with unicast. ??? :) ???

    My configuration is as follows:

    Server Configuration - SCCM R2 SP2 <All Roles>, SQL 2005, WDS - All on the same box
    Network configuration - DVMRP

    When my pxe client boots the TS negotiates a multicast session and downloads the package via multicast, extracts it, and applies it. Is this correct???

Answers

  • Saturday, November 07, 2009 8:16 PMJason SandysMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Multicasting isn't about reducing network load on a single system, it's about reducing network load on the network as a whole. In unicasting, a single, separate stream of data is sent to each and every system that has requested it. In multicast, a single stream, and only a single stream, is sent out from the server no matter how many clients are requesting it; anyone wanting the data in that stream "subscribes" to it and the network infrastructure ensures that all subscribers receive the content.

    In theory, yes the network load on the system sending the multicast stream could be reduced, but there are many factors that go into this and ultimately this is not really the goal of multicasting and should not be viewed as a benchmark for successful implementation or usage of multicasting.
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    • Marked As Answer byMikeFi Monday, November 09, 2009 4:43 PM
    •  

All Replies

  • Saturday, November 07, 2009 8:16 PMJason SandysMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Multicasting isn't about reducing network load on a single system, it's about reducing network load on the network as a whole. In unicasting, a single, separate stream of data is sent to each and every system that has requested it. In multicast, a single stream, and only a single stream, is sent out from the server no matter how many clients are requesting it; anyone wanting the data in that stream "subscribes" to it and the network infrastructure ensures that all subscribers receive the content.

    In theory, yes the network load on the system sending the multicast stream could be reduced, but there are many factors that go into this and ultimately this is not really the goal of multicasting and should not be viewed as a benchmark for successful implementation or usage of multicasting.
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    • Marked As Answer byMikeFi Monday, November 09, 2009 4:43 PM
    •