1
0
Fork 0
mirror of https://github.com/Luzifer/continuous-spark.git synced 2024-12-19 17:21:20 +00:00
Daemon intended to do continuous tests against a sparkyfish server
Find a file
2024-12-13 13:46:01 +01:00
.github/workflows Replace CI system 2024-12-12 12:44:08 +01:00
.gitignore Keep a local log of all measures 2017-07-28 07:13:51 +02:00
go.mod Fix: Refactor throughput test and fix calculation error from v1.1.0 2024-12-13 13:43:37 +01:00
go.sum Fix: Refactor throughput test and fix calculation error from v1.1.0 2024-12-13 13:43:37 +01:00
History.md prepare release v1.1.1 2024-12-13 13:46:01 +01:00
influx.go Modernize code, fix linter errors 2024-12-12 13:12:29 +01:00
LICENSE Fix LICENSE file 2019-01-27 15:30:01 +01:00
main.go Fix: Refactor throughput test and fix calculation error from v1.1.0 2024-12-13 13:43:37 +01:00
Makefile Add automated building 2017-07-28 07:23:09 +02:00
ping.go Modernize code, fix linter errors 2024-12-12 13:12:29 +01:00
README.md Breaking: Code cleanup, switch to InfluxDB for graphing 2019-01-27 15:25:13 +01:00
screenshot.png Add README 2017-07-28 07:22:15 +02:00
spark.go Fix: Refactor throughput test and fix calculation error from v1.1.0 2024-12-13 13:43:37 +01:00
throughput.go Fix: Refactor throughput test and fix calculation error from v1.1.0 2024-12-13 13:43:37 +01:00

Go Report Card

Luzifer / continuous-spark

This tool is a daemon intended to do continuous tests against a sparkyfish server. The measurements are sent to an InfluxDB for graphing and are stored locally in a TSV file for reference.

Why? Quite easy: My internet connection is quite often way slower (170Kbit vs. 200Mbit) as promised in the contract I'm paying for so I set up this daemon on my NAS connected using 2x1Gbit cable to my providers FritzBox. On the other side an unmodified sparkyfish server is running on a 1Gbit datacenter connection. The test is executed every 15m and looking at the graph causes me to weep...