You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far, we have only used latency tests mainly because they don't take as much time as latency tests and because they don't cause as much stress on the remote mirrors. It would still be beneficial to have the option to run bandwidth-tests when the user desires to do so – but not in an automated manner, like every time when Flexo starts.
Perhaps we could just provide an endpoint so that the user can run an HTTP POST request with curl in order to instruct Flexo to run bandwidth-tests.
The text was updated successfully, but these errors were encountered:
So far, we have only used latency tests mainly because they don't take as much time as latency tests and because they don't cause as much stress on the remote mirrors. It would still be beneficial to have the option to run bandwidth-tests when the user desires to do so – but not in an automated manner, like every time when Flexo starts.
Perhaps we could just provide an endpoint so that the user can run an HTTP POST request with curl in order to instruct Flexo to run bandwidth-tests.
The text was updated successfully, but these errors were encountered: