refactor: rename variables

Using `RTT` instead of `Latency` to be consistent with multiple other
RTT usages in code. I think mixing "Latency" and "RTT" will make some
readers of the code a bit confused.

Author: JensRantil

gradient.go

@@ -182,15 +182,15 @@ func (c *GradientController) update(r Execution) uint {
 		return queueSize
 	}
 
-	if c.resetNoLoadRTT || c.noLoadRTT > r.Latency {
-		c.noLoadRTT = r.Latency
+	if c.resetNoLoadRTT || c.noLoadRTT > r.RTT {
+		c.noLoadRTT = r.RTT
 		c.resetNoLoadRTT = false
 	}
 
 	// TODO: Remove this line and make this configurable to be logged or not.
-	log.Println("Reported latency:", r.Latency, "NoLoadRTT:", c.noLoadRTT)
+	log.Println("Reported latency:", r.RTT, "NoLoadRTT:", c.noLoadRTT)
 
-	gradient := maxf(0.5, minf(1.0, c.rttTolerance*float64(c.noLoadRTT)/float64(r.Latency)))
+	gradient := maxf(0.5, minf(1.0, c.rttTolerance*float64(c.noLoadRTT)/float64(r.RTT)))
 
 	fcurrLimit := float64(currLimit)
 	var newLimit float64

interfaces.go

@@ -17,7 +17,7 @@ type Notifier interface {
 
 type Execution struct {
 	InFlight uint
-	Latency  time.Duration
+	RTT      time.Duration
 	Err      error
 }