Open in1tiate opened 3 years ago
@in1tiate Is the video I have attached the lag that you're talking about? I don't think that it's any huge problem. Seems pretty on-par with how long things usually take to load on the internet?
tic = time.perf_counter()
c = self.client_manager.new_client(transport)
c.server = self
c.area = self.area_manager.default_area()
c.area.new_client(c)
toc = time.perf_counter()
print(f"Time to response was {toc - tic:0.4f} seconds")
I've timed the above code to see what it was looking like for creating a new client when the user clicks on the server and got:
Which is well within the range of the general UI/UX response time.
Thoughts??
The amount of lag is negligible when network latency is not a factor, however when it is a factor tsuserver can take upwards of 2 seconds to properly finish the handshake
The way you're explaining this makes it seem like it's a network latency problem and nothing with TSU? If the handshake with no latency is ~0.0011 seconds and with network latency is more, that's not an issue with TSU, right?
I don't remember which part of the handshake tends to take the longest, other than the initial TCP connection. Maybe look into the HDID/ban check.
tsuserver3 has about 1-2 seconds of lag between the user clicking the server entry and the handshake completion, even on local servers. Contrast this with akashi, which completes the handshake near-instantly on a local connection, and it's clear something is severely hampering performance here.