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

chat works, throughput or latency does not #3

Closed
matti opened this issue May 8, 2022 · 5 comments
Closed

chat works, throughput or latency does not #3

matti opened this issue May 8, 2022 · 5 comments

Comments

@matti
Copy link

matti commented May 8, 2022

running

$ weron chat --community mycommunity --password mypassword --key mykey --names user1,user2,user3 --channels one,two,three

on two servers works, but throughput or latency just "hangs":

mac $ weron utility throughput --raddr "wss://asdfasdf.fly.dev" --community mycommunity --password mypassword --key mykey --server
.wss://asdfasdf.fly.dev
{"level":"info","addr":"wss://asdfasdf.fly.dev","time":"2022-05-08T12:38:56+03:00","message":"Connecting to signaler"}
{"level":"info","id":"328100cc-6814-461f-b26b-b06e30eefb0f","time":"2022-05-08T12:38:56+03:00","message":"Connected to signaler"}
{"level":"info","id":"31deeab6-3281-4ec7-89bb-d3f7b243b863","time":"2022-05-08T12:39:00+03:00","message":"Connected to peer"}
linux $ weron utility throughput --raddr "wss://asdfasdf.fly.dev" --community mycommunity --password mypassword --key mykey
.wss://asdfasdf.fly.dev
{"level":"info","addr":"wss://asdfasdf.fly.dev","time":"2022-05-08T12:38:59+03:00","message":"Connecting to signaler"}
{"level":"info","id":"31deeab6-3281-4ec7-89bb-d3f7b243b863","time":"2022-05-08T12:39:00+03:00","message":"Connected to signaler"}
{"level":"info","id":"328100cc-6814-461f-b26b-b06e30eefb0f","time":"2022-05-08T12:39:00+03:00","message":"Connected to peer"}

another peer is mac with tailscale and other is linux with tailscale - does tailscale interfere?

@matti
Copy link
Author

matti commented May 8, 2022

oh, it works but is just slow - maybe the command should output something before 34s has elapsed?

1.459 MB/s (11.673 Mb/s) (50 MB read in 34.26586123s)
1.260 MB/s (10.078 Mb/s) (50 MB read in 39.691700195s)
1.354 MB/s (10.830 Mb/s) (50 MB read in 36.934796799s)

@matti matti closed this as completed May 8, 2022
@pojntfx
Copy link
Owner

pojntfx commented May 8, 2022

@matti matti reopened this May 9, 2022
@matti
Copy link
Author

matti commented May 9, 2022

reopened then

@pojntfx
Copy link
Owner

pojntfx commented May 15, 2022

@matti Thanks for you suggestion; I've added the following log messages on the Debug level, which should show that the system is in fact doing something:

{"level":"debug","channelID":"weron/throughput/primary","peerID":"39e1cb10-6b0d-412e-8711-bce1112d89e9","time":"2022-05-15T17:07:12+02:00","message":"Started receiving data"}
{"level":"debug","channelID":"weron/throughput/primary","peerID":"39e1cb10-6b0d-412e-8711-bce1112d89e9","time":"2022-05-15T17:07:14+02:00","message":"Acknowledging received data"}

Be sure to set the verbosity level appropriately (--verbose 6) and feel free to reopen if the solution isn't working appropriately.

@matti
Copy link
Author

matti commented May 15, 2022

awesome, thank you!

pojntfx added a commit that referenced this issue Feb 26, 2023
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

No branches or pull requests

2 participants