Investigate why config requests take so long to complete

Issue #211 resolved
Saxon Milton created an issue

It was found that a 10 → 20 second modification of the netsender http client timeout was required to get the config requests to work without exceeded the timeout. This seems weird given that 10 seconds should already be enough especially with a good connection speed. We should investigate why config requests take so long to complete and if there’s anything we can do about it.

Comments (1)

  1. Alan Noble

    No longer reproducible.

    Possibly due to VidGrind being overloaded at the time, due to being constrained to run a single instance, which is no longer the case.

  2. Log in to comment