get-closer helps you to find out closest hosts in terms of network latency or application performance.
Warning: project is under heavy development, feel free to open an issue
Network services are very sensitive to latency degradation. In era of cloud computing we can get the same services from different providers that will have different locations, so network distance will differs too.
Choosing an optimal performing endpoint is vital part of optimization.
We wanted an easy way to compare different endpoints in case of network latency or application performance.
go get -u github.com/akme/get-closer
How to use
Find out closest hosts in terms of network latency. Usage: get-closer [command] Available Commands: dns Measuring domain resolve time via DNS resolver help Help about any command http Measuring time for HTTP request. icmp Measuring RTT for hosts from list. tcp Measuring time for connecting to open TCP port. Flags: -c, --concurrency uint concurrency (default 1) --config string config file (default: ~/.get-closer.yaml) --count int number of tests per host (default 1) -d, --delay int set delay between checks (default 3) -r, --dns-resolver string use custom DNS resolver -w, --dns-warm-up warm up DNS cache before request (default true) -f, --from-file string path to file with hosts to check -h, --help help for get-closer -l, --limit uint number of hosts to return -b, --progress-bar show progress bar (default true) -t, --timeout uint timeout for request (default 60) -v, --verbose enable verbose mode Use "get-closer [command] --help" for more information about a command.
This repo contains hosts.txt and dnsresolvers.txt as an example of hosts file that you can use for test runs.
get closer ping -f hosts.txt
get closer tcp -f hosts.txt
get-closer http -f hosts.txt
get-closer dns -f hosts.txt
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
There is no documentation for this package.