none
Rate Limits RRS feed

  • Question

  • In SCCM is there a good article on exactly how the rate limits work?

    What I mean is it doesn't appear to be percentage of "Available" bandwidth it is using.

    From reading around it looks like it may be calculating and using a certain percentage no matter how much is utilitized?

    So for example if my link is 80% utilized and I have SCCM set to use 25% then it seems like I would then go over 100% because sccm would be sending for a full 25% of the time, not 25% of available bandwidth, which in my example would be 5%.  100-80=20 and 75% of 20 is 5%.

    But anyway, would be great if there was a very technical document outlining exactly how this feature works in SCCM.

    Thanks,

    Terry

    Monday, June 21, 2010 9:19 PM

Answers

  • Personally I've never liked the rate limits in SCCM and I never use them. I leave it up to the network guys to set QOS to throttle traffic. It's much more effective that way. The way SCCM works, let's take for example you set 50%, SCCM sends a chunk of data, measures how long it takes to send it, waits that same amount of time then sends another chunk. The result is that SCCM fully utilizes your bandwidth 50% of the time, not SCCM uses 50% of your bandwidth 100% of the time. So you get these up and down spikes in traffic that will still causes complaints.

     

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    • Marked as answer by mattw112 Wednesday, June 23, 2010 11:05 PM
    Tuesday, June 22, 2010 4:14 PM
    Moderator

All replies

  • Does this not give you what you want?

    http://technet.microsoft.com/en-ca/library/bb694241.aspx

     

     


    http://www.enhansoft.com/
    Monday, June 21, 2010 10:00 PM
    Moderator
  • Personally I've never liked the rate limits in SCCM and I never use them. I leave it up to the network guys to set QOS to throttle traffic. It's much more effective that way. The way SCCM works, let's take for example you set 50%, SCCM sends a chunk of data, measures how long it takes to send it, waits that same amount of time then sends another chunk. The result is that SCCM fully utilizes your bandwidth 50% of the time, not SCCM uses 50% of your bandwidth 100% of the time. So you get these up and down spikes in traffic that will still causes complaints.

     

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    • Marked as answer by mattw112 Wednesday, June 23, 2010 11:05 PM
    Tuesday, June 22, 2010 4:14 PM
    Moderator
  • Thanks,

    So it doesn't appear this is working that way, in the sender log just says over and over again "waiting 1 second" between sends.  no matter what I set the percentage to.  Although I do see it recognizing the percentage changes.

    Maybe the link isn't slow enough and it is just not taking very long to send.  but this is one of our slower links.  Anyway.

    John you are right QoS is preferable, but right now QoS is only Implemented on half the network.  So until then we are trying to use what we have to make it work.

    Thanks,

    Terry

    PS - John marking you as the answer, even though you said exactly what was int he technet article, you said it with more personal insight and less links.

    Wednesday, June 23, 2010 11:05 PM
  • There's a hotfix for this. If you are SP2 and you haven't installed it on every server SCCM will  ignore the settings. KB978021

     

     

     

     

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    Thursday, June 24, 2010 12:18 PM
    Moderator
  • Hi Thanks John,

    Dont think this is it.  First this is a brand new environment, just built and all servers are and always have been SP2 R2.

     

    From the KB article I think this is different too.  "Number of retries" and "Delay before retrying (minutes)" retry settings.. I think are different than the retries done to make the throttling work....

     

    Terry

    Thursday, June 24, 2010 4:17 PM