(imported topic written by tgxwtso91)
Each month we push out patches the Network Admin expresses concern about bandwidth being taken up by Big Fix. I would like to know how to determine the size of the payload going out to each agent/workstation as part of a baseline’s action. We typically spread these out over 120 minutes.
(imported comment written by BenKus)
Hey tgxwtso,
If you are using relays in each location with with limited WAN bandwidth, then the WAN bandwidth should be minimal… but to answer your question, there are lots of details that would need to be looked at including the size of the packages, the placement of relays, the number of computers, etc.
Ben
(imported comment written by tgxwtso91)
Thanks,
For each deployment of a baseline that includes multiple fixlets, is their a way (other than adding up the files sizes of each fixlet in the fixlet panel) to see what the payload would be to a single computer. Also do I have the right understanding that, lets say, total payload of a baseline is 10mb and I set my deployment to span 120 minutes, then each client will use that 120 minutes to get the baseline.
(imported comment written by jessewk)
You can run the following query in the presentation debugger, replacing ‘Test Baseline’ with the name of your baseline:
(it as string & " MB") of (it / (1024 * 1024 as floating point)) of sum of download sizes of source fixlets of components of component groups of bes fixlet whose (baseline flag of it AND name of it = “Test Baseline”)
When you set the ‘Distribute over X minutes’ option in the console, the behavior is different than you describe. What will happen is that once the action becomes relevant, each client will chose a random time between 0 and X minutes before it starts downloading the files. How long it will take to actually do the download is dependent on network speeds, your relay architecture, and any of the many bandwidth throttling options you may or may not have configured.
Jesse