-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
network transfer between two nodes very slow #3825
Comments
@satra Hrm... This is a bit of a known problem. The dht overhead here is pretty annoying (something i'm planning on improving with: #3786). What is the normal transfer speed between the two machines in question? What is the latency between the two machines? What is the actual bandwidth utilization of each machine vs how fast the transfer appears to be going? |
@whyrusleeping - sorry about the delay. had a chance to upgrade to 0.4.9 and test out latencies and bandwidth. ping latency:
an scp command:
ipfs command translates to about 20MB/minute
|
@whyrusleeping and @Kubuxu - any ideas on how to improve throughput? |
#3867 was merged so it should be better now. You can build go-ipfs from current master and see if it improves things for you. |
@magik6k - will check it out and report back the numbers. |
You may also want to start the daemon with |
@Kubuxu - ok this is much faster. i'll keep playing with and see if things are better. |
Hello Do you think IPIPFS is good to make a chat soluton like IM messenger like Telegram and very much fast ? |
@Kamelia2000 please ask support questions on https://discuss.ipfs.io (also, in general, please keep issue comments on-topic) |
Version information:
server:
go-ipfs version: 0.4.6-
Repo version: 5
System version: amd64/linux
Golang version: go1.8
client:
go-ipfs version: 0.4.6-
Repo version: 5
System version: amd64/darwin
Golang version: go1.8
Type: bug
Priority: P3
Description:
on the client:
and this transfer is very slow.
the server sits on a large bandwidth connection and if i simply use rsync to download the ipfs directory it's much much faster.
is there a way to determine what the client and the server are spending their time on?
@whyrusleeping - it almost seems like the
ls
issue we were seeing. that it won't start retrieving anything till it does anls
and then takes forever to download the 1.5G of data.The text was updated successfully, but these errors were encountered: