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

feat: Performance Improvements and Accurate UI #31

Merged
merged 5 commits into from Oct 19, 2022
Merged

feat: Performance Improvements and Accurate UI #31

merged 5 commits into from Oct 19, 2022

Conversation

bennjii
Copy link
Member

@bennjii bennjii commented Oct 19, 2022

Now shows your current tier whilst also pulling your current usage maximums, allowing implementation of known disconnect reasoning, i.e. will not connect free or supporter tiers who have exceeded maximums and will be thrown by server.
Also improves connection times:

  • 1000ms average reseda connection
  • 2000ms average windows service startup

Resulting in an average 3s connection time, on unix machines this can possibly be reduced. The base time requirement is the reseda connection, which depends heavily on the distance to the connecting server- i.e. at a 200ms ping-to-server, the connection takes 800ms to propagate and 200ms of computing time, thus 1000ms. The windows service startup is a standard time restraint that cannot be mitigated under the current implementation but should be amendable using a different method.

@bennjii bennjii merged commit b925664 into master Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant