public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raffaele BELARDI <raffaele.belardi@st.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] network transfer speed
Date: Fri, 15 Jan 2021 08:11:08 +0000	[thread overview]
Message-ID: <DB8PR10MB3306E8F28A3B026320448938F7A70@DB8PR10MB3306.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <f0984b50-cc2c-89c8-dd89-e97d2475a083@sys-concept.com>

> -----Original Message-----
> From: thelma@sys-concept.com <thelma@sys-concept.com>
> Sent: Friday, January 15, 2021 07:57
> To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
> Subject: [gentoo-user] network transfer speed
> 
> 
> 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?

If the PCs attached to the switch show 1000 then the switch _is_ gigabit.

On my 1Gb home network I have an FTP transfer speed between Gentoo PCs A and B of almost 900Mbps, the other way round is almost half of that. One difference between the two systems is the disk, A uses SATA-2 disk while B has SATA-3.

Does the 'B' in 110MB/s stand for byte? If so you have 880Mbps which is not bad, the problem probably lies somewhere else. Otherwise you could check the switch error count (if you have a managed switch) or the network card error count, just to ensure you don't have a cabling/connector problem.

Have you tried other transfer methods just for comparison? I think FTP is still the fastest way to transfer files, though insecure or inconvenient as it might be. I have no experience with rsync.

raffaele

  parent reply	other threads:[~2021-01-15  8:11 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
2021-01-16 18:55               ` Michael
2021-01-16 20:27                 ` thelma
2021-01-15  8:11 ` Raffaele BELARDI [this message]
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=DB8PR10MB3306E8F28A3B026320448938F7A70@DB8PR10MB3306.EURPRD10.PROD.OUTLOOK.COM \
    --to=raffaele.belardi@st.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