Honestly, this only really helps people in rural areas. The vast majority of urban 5GHz implementations are at 80MHz - 6GHz does allow for 160MHz channelization, but at 320MHz the attenuation is so great that most homes will require multiple APs to actually hit appropriate MCS indexes.
Fot at home, I tend to stick with 2.4 GHz. It is slower, but with a <100 Mbit uplink to the internet, local speed does not matter. 2.4 does just work better with less APs and thicker walls.
2.4 GHz is unreliable for me these days due to interference from bluetooth headphones and hearing aids that other people are using. The issues tend to only show up during extended periods of video streaming, and having looked at a bunch of traffic captures over the holidays, it seems to be limited to certain streaming services sending very large bursts of traffic at extremely high rates (likely from servers with 100+ Gbps interfaces using TSO to reduce CPU usage). That makes me think that the regularly paced bluetooth interference from real time audio streams limits the maximum viable burst size of a 2.4 GHz wifi radio.
Yes, this happened a bunch more over the Christmas holiday when we had an extra 3 or 4 younger family members all listening to music and videos over their bluetooth ear buds and headphones, which made it much easier to track down as it was quite a rare intermittent failure with only a single bluetooth device being active.
This also only works if you're not living in an apartment building. Even then, there's Bluetooth and other things that don't share spectrum nicely with 802.11.
Having lots of lower powered routers is actually better for interference.
MacOS won't roam properly unless the signal from the connected AP drops below -75db, so cranking the power on all your APs will give you worse performance if you move around.
My point was that some businesses are tying their destiny to nix - in my experience this is a sign that an open-source project will gain corporate benefactors keeping it afloat + making it safer for others to adopt.
I encourage playing with these + cumulus linux via the nvidia air lab environment. It may seem limiting at first, but being able to upload a graphviz topology as part of a CI/CD pipeline is extremely powerful.
This is not quite true - GPU's are limited to select VM types, and the number of GPU's you have influences the maximum number of cores you can get. In general they're only available on the n1 instances (except the a100's, but those are far less popular)
