Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate latency effect on websocket #515

Closed
Terkwood opened this issue Jun 25, 2021 · 1 comment
Closed

Investigate latency effect on websocket #515

Terkwood opened this issue Jun 25, 2021 · 1 comment
Labels
bug Something isn't working research Something to tinker with

Comments

@Terkwood
Copy link
Owner

Terkwood commented Jun 25, 2021

I wonder if a high latency is causing #513. We could investigate this in a couple of ways:

  • purchase a VPN and route requests thru it
  • deploy a test instance of gateway to a faraway land

Additionally, it would be nice if the browser could somehow report latency metrics to the backend, so that we can understand whether failure events seen in #513 coincide with high latency

@Terkwood Terkwood added bug Something isn't working research Something to tinker with labels Jun 25, 2021
@Terkwood
Copy link
Owner Author

It can still fail from an Azure server in USA. The websocket is flaky under a variety of circumstances! 😵

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working research Something to tinker with
Projects
None yet
Development

No branches or pull requests

1 participant