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

FTR: Measure Server-Client Latency #322

Open
proof88 opened this issue May 17, 2024 · 0 comments
Open

FTR: Measure Server-Client Latency #322

proof88 opened this issue May 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@proof88
Copy link
Owner

proof88 commented May 17, 2024

Although GNS measures latency between server and clients, it is just the low level latency.
Higher level stuff such as PGE's incoming packet buffer, rendering delay, etc. is not calculated, but it would be interesting to see the overall latency between high level layer of server and client.
So a new message should be introduced which is periodically exchanged between server and client:

  • tS0: timestamp of server sending out the message to client;
  • tC0: timestamp of client receiving that message from server and when client sends the answer at high level;
  • tS1: timestamp of server receiving message from client, and responding back to client (it also sends back value of tS1-tS0);
  • tC1: timestamp of client receiving the 2nd message from server, for it it sends back value of tC1-tC0 to server.

This way server can display the higher level latency between server and client which is tS1 - tS0, and client's calculation tC1 - tC0.
Client can also display the latency between client and server which is tC1 - tC0, and server's calculation tS1 - tS0.

Not sure on the long run how this will be useful but definitely adds some value for debugging and/or benchmarking purpose in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant