search

Kong / mesh-perf

Performance tests of Kong Mesh
Apache License 2.0
0 stars 1 forks source link

should propagation time include action #191

Open lahabana opened 1 month ago

lahabana commented 1 month ago

At the moment we wait for pods to be available (or policy to be applied) before computing the propagation time.

https://github.com/Kong/mesh-perf/blob/286a0cd324634f5e9a54c0bbc8c16a4cc9e5c392/test/k8s/simple_test.go#L214-L230

Should we include that time? If we do we'll be sensitive of the time it takes to start a pod so platform dependent. However, this is a stat that's more useful to users than what we have today.

Another option is to watch for change to endpointSlice and count from there. This would sum up as "how much longer does it take for an endpoint to be added compared to core k8s" though that wouldn't even be exact...

lobkovilya commented 1 month ago

Triage: regardless of the approach we pick using WaitNumPods is not accurate enough as it's using a loop with sleeps. Probably we should watch an endpointSlice and start the timer when the endpoint is added.