From: bobwxc <bobwxc@88.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] network transfer speed
Date: Fri, 15 Jan 2021 16:42:16 +0800 [thread overview]
Message-ID: <e329c6ff-6a5c-de69-bb65-78cf580a717c@88.com> (raw)
In-Reply-To: <DB8PR10MB3306878E52F8FEAB74B5F136F7A70@DB8PR10MB3306.EURPRD10.PROD.OUTLOOK.COM>
在 2021/1/15 下午4:27, Raffaele BELARDI 写道:
>> -----Original Message-----
>> From: bobwxc <bobwxc@88.com>
>> Sent: Friday, January 15, 2021 08:57
>> To: gentoo-user@lists.gentoo.org
>> Subject: Re: [gentoo-user] network transfer speed
>>
>> 在 2021/1/15 下午2:56, thelma@sys-concept.com 写道:
>>> On both of my systems the network card speed is showing 1000
>>> cat /sys/class/net/enp4s0/speed 1000
>>>
>>> but when I do rsync larage file I only see about: 20 to 22MB/s On my
>>> home network I get about 110MB/s between PC's
>>>
>>> Both PC's have SSD and the swith is Gigabit (I think).
>>> How to find a the bottleneck?
>> 1000Mbps network card's maximum theoretical speed is about 125MiB/s.
>> It only works in short distances.
> Correct but that's the line speed that you'll never reach, when you take into account Ethernet frame overhead, IP (and possibly TCP) header overhead and application ( rsync, FTP, SMB, NFS) overhead you get lower figures. In my experience 900Mbps (110MiBps) on a 1000Mbps line is more realistic for 'normal' transfers.
>
Yes, you are right. So it is just *theoretical* speed :-)
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.
next prev parent reply other threads:[~2021-01-15 8:42 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 [this message]
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
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=e329c6ff-6a5c-de69-bb65-78cf580a717c@88.com \
--to=bobwxc@88.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