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
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
@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?
Attorney.Online.2.2021-04-18.18-36-10.mp4
tic=time.perf_counter()
c=self.client_manager.new_client(transport)
c.server=selfc.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.
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?
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.
The text was updated successfully, but these errors were encountered: