127
edits
| Line 32: | Line 32: | ||
If traffic considerations are relevant, the following options exist to reduce overall server/network load: | If traffic considerations are relevant, the following options exist to reduce overall server/network load: | ||
* configure a relatively low "server.out_of_reach" value, so that clients outside a certain range are no provided with updates | * configure a relatively low "server.out_of_reach" value, so that clients outside a certain range are no provided with updates (usually about 100 nm on the main server network) | ||
* for virtual gatherings (i.e. fly-ins), have clients use airports and places that do not have lots of other traffic (i.e. in other words, avoid places like standard airports such as KSFO) | * for virtual gatherings (i.e. fly-ins), have clients use airports and places that do not have lots of other traffic (i.e. in other words, avoid places like standard airports such as KSFO) | ||
* avoid the use of unnecessary relay servers | * avoid the use of unnecessary relay servers | ||
* if you are not interested in your server being publicly available, only share its address with your friends privately | * if you are not interested in your server being publicly available, only share its address with your friends privately | ||
* for local testing/development purposes, you may want to run only a private fgms session, that may be specific to your LAN or even computer | * for local testing/development purposes, you may want to run only a private fgms session, that may be specific to your LAN or even computer. | ||
= Getting fgms = | = Getting fgms = | ||
edits