Problem description

Our IPSec tests use the migrate-svc app to detect whether or not there have been packet drops when doing upgrades or key rotations. This app includes a 500ms sleep, included to avoid saturating the system. The wait time was arbitrarily picked, no investigation was done as to how much to wait.

It would be worth reducing the time or even completely removing the sleep, because we currently miss catching some drops that are visible when using the more intensive httpperf instead.

Implementation suggestion

Whoever is doing this work, should check that the system doesn't get overloaded. And to make this easier it would make sense to make the sleep amount a parameter to the migrate-svc app, and then iterate from the testing side.