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

Disproportion between bandwith speed limiter and the actual internet speed of the client #5902

Open
m1hc1u opened this issue Oct 30, 2023 · 8 comments

Comments

@m1hc1u
Copy link

m1hc1u commented Oct 30, 2023

Describe the bug
My ISP provides me with 450 Mb/s download speed and 50 Mb/s upload speed. We've conducted few tests via Mysterium Dark with my contact who is ~ 100km away within same country. He has 600 Mb/s download & 300 Mb/s upload speed.

We made 4 tests and I used "Limit bandwith to..." under Node UI\Settings\Traffic menu. ⁠#node-runners-general

Test # 1 - Limit bandwith to 50 Mb/s
Test # 2 - Limit bandwith to 100 Mb/s
Test # 3 - Limit bandwith to 250 Mb/s
Test # 4 - Limit bandwith to 400 Mb/s

There were none other connections with my node during tests - only my contact.
As you can see, the difference between chosen limit and client's speeds are at least 9x lower than expected.

To Reproduce
Steps to reproduce the behavior:

  1. Connect with my node
  2. Use speedtest to check the bandwith

Expected behavior
Almost none disproportion between limited bandwith setup and contact's speed.

Screenshots
Test # 1 https://cdn.discordapp.com/attachments/1096784581732093962/1167583754580148224/50mbps.png?ex=654ea81b&is=653c331b&hm=d2de60b1790d1a55b724e3f73d6cb06c35a7ceb5bc98812265f41cf899d12a4c&
Test # 2 https://cdn.discordapp.com/attachments/1096784581732093962/1167583754831790100/100mbps.png?ex=654ea81b&is=653c331b&hm=e628bb502d902d270b4309b153def0eb11ba368cc6a691cc2a97e370bef0529d&
Test # 3 https://cdn.discordapp.com/attachments/1096784581732093962/1167583755146383381/250mbps.png?ex=654ea81b&is=653c331b&hm=e49002f2619b10775a40a5cc0e422f203e799305c9204eb1cce398bc73ddf121&
Test # 4 https://cdn.discordapp.com/attachments/1096784581732093962/1167583755452563517/400mbps.png?ex=654ea81b&is=653c331b&hm=1109c5bf731010ab1c3faebd52e1c084e7a8b6eb350b3afc1d2a06ffa72126b9&

Environment (please complete the following information):

  • Node version: 1.27.0
  • OS: Mystberry
  • Your identity (if applicable): 0xcdbd3c67742921337abddcadb484f1f17faa6bd2
@m1hc1u m1hc1u added the bug label Oct 30, 2023
@lusine-h
Copy link

lusine-h commented Nov 8, 2023

I tried reproducing the issue but I couldn't see the exact results as my connection is slower than the user had. For the provider it is 54 download and 40 upload and for the consumer 15 download and 6 upload. I was able to test only with slower values, limited provider with 15 mb and while connection for the consumer the speed was 12 download and 5 upload. If the issue which user reported happens also for me I should see about 2 mb speed but I see normal speed for the limit I set.

@adinetech
Copy link
Member

I conducted tests with varying bandwidth limits, and the results are as follows:

No Bandwidth Limit:
Test Latency: 47ms
Download and Upload Performance: 52.32 Mbps download, 135.31 Mbps upload.

Bandwidth Limited to 15 Mb/s:
Latency during test: Higher than baseline
Download and Upload Performance: 0.9 Mbps download, 1.69 Mbps upload.

Bandwidth Limited to 101 Mb/s:
Latency during test: Slightly higher than baseline
Download and Upload Performance: 11.04 Mbps download, 11.98 Mbps upload.

image
image
image

@ZygintasBudrys
Copy link

Severity: Major
Priority: High

@tzununbekov
Copy link
Contributor

@m1hc1u we've merged the fix and released the patched version of the node. Please update to the latest version (1.29.7) and let us know if it solves the issue or if the problem persists

@ZygintasBudrys
Copy link

@lusine-h please try to reproduce it

@lusine-h
Copy link

lusine-h commented Mar 6, 2024

Was not able to reproduce. Maybe the reason is my slower connection compared with user who reported about this.

Copy link

stale bot commented Jun 5, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 5, 2024
@adinetech
Copy link
Member

Could this be tested by running a node on a datacenter?

@stale stale bot removed the stale label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants