Provide the ability to set the number of PullDP that can download at the same time.
By providing this settings, it would ease up massive distribution of a package to many PullDP.
A setting similar to Concurent download on DP would be perfect!
As of now, updating a package hosted on 1000 PullDP will trigger all PullDP at the same time to update the package.
This cause high CPU and IO on the server as well as potential network load.
Jo
shared this idea
The best way to control this is make a mesh of pull-DPs, and have some pull from other DPs… as opposed to all from the siteserver. That offloads network bandwidth from the siteserver
2 comments
-
Anonymous
commented
You can't always mesh. There are certain cases where server placement is allowed only in one datacenter and pull dps will have to pull from that specific location. Current design is not flexible so you can easily saturate the pipe in the datacenter
-
Anonymous
commented
Thanks for the suggestion. In scenario like in Retail, it some time can't be possible as all store (pullDP) communicate only with the head office. Additionnal note : it could be only better known process of how all this is processed. I've seen difference on how SCCM 2012 R2 and 2012 R2 SP1 handle large distribution.
In 2012 R2 : it seemed like concurrent sending was stock at around 70 PullDP.
In 2012R2 SP1 : it seems more like all or close to for concurrent sending.PS : I,ve followed the distribution in the content status