Please add "--max-bitrate" option...
-
HI,
A lot of multicast problems comes from overload network and mixed speeds. Multicast hang, fail or simply does not start waiting for answers that will never come. Timeouts are legions… All those problems can be resolved by adjusting “–max-bitrate” parameter in the getId udpsender command in “MulticastTask”. For example, in a mixed 1000/100 network, we can adjust udpsender with “–max-bitare 80m” parameter. I’m new to this project and i’m not good enough in coding to modify source code to add this option in the web interface and into the options. Could you add please a --max-bitrate setting into the web interface to adjust udp-sender command ?
-
@Jean-Jacques-Morda Actually, I think you are good enough to modify the code. Most people don’t even know what udpsender even is. Ever hear of grep? Bet you could find all the udpsender commands-in-code throughout your system in a minute or two with something like:
find / | grep udpsender
Or some other variant of a search command.
If the devs did modify the code, it’d be in FOG Trunk only. So you’d need to move to FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
-
Hello,
Thank you for your replay. My problem is not to find where the udpsender command is generated (getId from MulticastTask) but is to modify the php code to add an array in fog settings. I love the fog project and i’ll participate in the code as soon as i understand all of this… i did not code for years and i have it a little hard… also i am a noob with all github things but i’ll read the doc to understand how to submit a change…
-
@Jean-Jacques-Morda As a side thought to all this,
Because you have a 1000/100 mixed environment, maybe you should not group your machines just by model…
Maybe… say… you have a building full of nothing but Dell 9020s.
So… You’d actually have two different groups for those… 9020s with gig, 9020s without gig… Don’t mix computers with different link speeds… keep them separated in their own groups - this should solve your issues.
-
@Wayne-Workman In fact, it’s more complicated than that… i have many different switches with many different links / configurations on many different machines (mostly HP), somewhere computers in one room was connected to two or three different switches and some of switches are not configured by me but by another service that did not understand our needs. So i’m only in charge of my own switches but not VLAN ones. Some computers are far far away from the server and multicast transits in many many switches configured in differents ways because computers network card don’t act the same way if half/full duplex enabled generating lot of collisions… so, if the speed is not limited by 80m max-bitrate, timeouts rules the network traffic and udpsender no longer follows.
-
@Wayne-Workman but with --max-bitrate 80m, my 160gigs images are working like a charm with multicast download in our classrooms ! I’m happy with that.
-
@Jean-Jacques-Morda Understood… It does sound complex. But, I’ll add that - instead of dealing with the complications of multicast, you are highly likely to get them all imaged in roughly the same amount of time if you simply just used unicast.
Plus, there are incredible speed boosts in FOG Trunk. I can deploy a 40GB image to a machine in 5 minutes.
-
I’m cloning a classroom, 160 GO image in 2 hours. That is satisfactory for a so bad network such mine …
-
I’ve implemented the requested feature, but I do NOT know if it will work.
To set the bitrate, it’s a Per Node (master of course) setting.
You can set it how you see fit, appropriate to the way it’s set to the command. meaning you can setup the variable with 1000000, 1000k, or 1M
-
@Tom-Elliott Thank you, i’ll check the git to learn how you add it by the way and telle you results of my tests. I’ll check all of that tomorrow.
-
@Tom-Elliott Ok, don’t find the bitrate option until i remember it’s a master node option… tested and glad to see the new option appear in the udpsender command ! Thanks again.
-
@Jean-Jacques-Morda said:
ption until i remember it’s a master node option… tested and glad to see the new option appear in the
I saw the new option on a system I was helping with last night… I didn’t know what to set it to, lol.
So I set it to 1000000
-
my needs is 80m so i set it to 80m and all is ok now for my network !!!
-
@Wayne-Workman said:
@Jean-Jacques-Morda said:
ption until i remember it’s a master node option… tested and glad to see the new option appear in the
I saw the new option on a system I was helping with last night… I didn’t know what to set it to, lol.
So I set it to 1000000
That means you limited its speed to 1Mbps.
You can set by 1000000 (bit)
You can set by 1000k (kilobit)
You can set by 1m (megabit) -
@Tom-Elliott crap.
-
@no1bossman You might want to stick an “m” in the max bitrate field for the storage node.
-
@Tom-Elliott What happens if the field is left blank?
-
–max-bitrate is not set and udp-sender auto selects the speed.
-
@Wayne-Workman yes, it detect the max theoretical speed… like speed on road. On road, sometime, we have to slow down to avoid accidents, if not, cars does not arrive to destination.
-
Hehe, don’t want to abuse but is a “per group” --max-bitrate option is possible ? Some computers groups are connected to a part of the network that need to be limited with --max-bitrate and some others not. Not very important but it will avoid to change master node setting when we launch cloning with another group. I suppose it’s a little bit more complex to implement