From: thelma@sys-concept.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] network transfer speed
Date: Fri, 15 Jan 2021 15:43:36 -0700 [thread overview]
Message-ID: <a5d7af51-4b9f-b4dc-db4d-966b472771cc@sys-concept.com> (raw)
In-Reply-To: <17080d29-e525-9cec-da43-2702b0de9aca@users.sourceforge.net>
On 1/15/21 9:55 AM, Jack wrote:
[snip]
>>>>
>>>> I don't know where does the file he sync from.
>>>> If you sync a file from a server in other city, for a 20 to 22MB/s speed
>>>> is very normal. But if in home, that is not good.
>>>>
>>>> And for ftp and rsync.
>>>> ftp is better for transferring a single large file once.
>>>> rsync is better for a long-term, incremental synchronization. The
>>>> file verification of rsync may take a lot of time for first sync.
>>> There is a theoretical network speed as already mentioned. There is a
>>> protocol speed, which may limit throughput if it has e.g. heavy encryption/
>>> compression and the CPU is anaemic. Finally, there is a MoBo bus (SCSI/SATA/
>>> USB) and the media storage limit. If using USB 1.1 or 2.0 and/or the disks
>>> are slow or experience write amplification, you'll find this will constrain
>>> the final transfer speed significantly.
>> The computers on this network are 2-meters apart and they both use SSD Drive (so USB limitation doesn't come under consideration).
>> Like I said, on my home network when I transfer the 24GB file I get about 110MiBps transfer, so I was expecting the same in remote location).
>> Some units are connected to a router Ausus RT-AC66U B1 but these ports are gigabit too.
> When you say the computers are remote, is it possible the file is passing through your local computer on the way between the two remote machines? Where are you actually running the rsync command?
The fact that I'm logged via ssh over VPN to a remote network should not have any influence over network speed.
I just made a loop:
Network A ==> Internet ==> Network B
ssh back to Network A over internet and run "rsync" I got same speed (as if I run the command locally) on Network A 112MB/s
So the limiting factor is somewhere else.
next prev parent reply other threads:[~2021-01-15 22:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 6:56 [gentoo-user] network transfer speed thelma
2021-01-15 7:49 ` Hogren
2021-01-15 8:34 ` Raffaele BELARDI
2021-01-15 13:26 ` Hogren
2021-01-15 14:13 ` Michael
2021-01-15 16:38 ` thelma
2021-01-15 7:57 ` bobwxc
2021-01-15 8:27 ` Raffaele BELARDI
2021-01-15 8:42 ` bobwxc
2021-01-15 9:58 ` Michael
2021-01-15 16:51 ` thelma
2021-01-15 16:55 ` Jack
2021-01-15 17:36 ` thelma
2021-01-15 22:43 ` thelma [this message]
2021-01-16 18:55 ` Michael
2021-01-16 20:27 ` thelma
2021-01-15 8:11 ` Raffaele BELARDI
2021-01-15 22:56 ` thelma
2021-01-15 23:38 ` William Kenworthy
2021-01-16 0:49 ` Manuel McLure
2021-01-16 4:00 ` Adam Carter
2021-01-16 20:36 ` thelma
2021-01-16 20:59 ` Jack
2021-01-17 10:51 ` Michael
2021-01-18 7:57 ` Raffaele BELARDI
2021-01-18 8:46 ` J. Roeleveld
2021-01-18 9:58 ` Raffaele BELARDI
2021-01-18 10:19 ` J. Roeleveld
2021-01-18 11:41 ` bobwxc
2021-01-18 19:13 ` thelma
2021-01-19 7:46 ` Raffaele BELARDI
2021-01-19 15:15 ` thelma
2021-01-19 14:11 ` J. Roeleveld
2021-01-19 14:34 ` Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5d7af51-4b9f-b4dc-db4d-966b472771cc@sys-concept.com \
--to=thelma@sys-concept.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox