From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Slow network transfers ... lost interrupts because of clocksource?
Date: Fri, 27 Sep 2013 12:33:37 +0200 [thread overview]
Message-ID: <52455F01.4060102@xunil.at> (raw)
I am back from my visit at a customer where I installed a new and shiny
gentoo server for running VMs (KVM).
Currently I don't have access as my VPN only works from my static IP at
home (my router seems to be offline right now ... and I am still away
from office for the weekend) so I can't check details now ...
basically:
I tried to copy/rsync some file with ~8GB over a gigabit connection ...
from old to new server. Checked ethtool for gigabit, looked ok. I always
saw the behavior that the transfer started rather fast and slowed down
within minutes. Let's say ~50 MB/s in the start and then down to maybe 2
or so. That is way from the expected throughput with such new hardware.
The NICs in the new server are BCM-something, Broadcom, using the tg3
Tigon module (exact model not available right now as mentioned above).
In "dmesg" I see lines like
hpet1: lost 1 rtc interrupts
which makes me wonder if that leads to the lousy performance (btw, I
fear slow virtualization performance as well).
Dealing with HPET I checked for kernel support and also added kernel
options to GRUB:
hpet=force clocksource=hpet
which lead to
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
hpet
I am unsure if I should further investigate things around this HPET-issue?
My thinkpad here shows "tsc" as clocksource ... good/better ?
What direction to go? force or disable HPET?
-
btw I saw the same slowdown on 2 NICs: one connects the server to the
LAN via GB-switch, the other connects the 2 servers directly via
crossconnect-cable (dedicated for backups).
I tried rsync with various options, scp, and even some tar/netcat-combo ...
The system runs gentoo sources 3.10.7, amd64 ...
-
Thanks for any thoughts on this!
Stefan
next reply other threads:[~2013-09-27 10:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 10:33 Stefan G. Weichinger [this message]
2013-09-27 13:02 ` [gentoo-user] Re: Slow network transfers ... lost interrupts because of clocksource? Nicolas Sebrecht
2013-09-27 13:06 ` Stefan G. Weichinger
2013-09-27 13:18 ` Nicolas Sebrecht
2013-09-27 15:05 ` Stefan G. Weichinger
2013-09-27 15:55 ` [gentoo-user] " Volker Armin Hemmann
2013-09-29 14:37 ` Stefan G. Weichinger
2013-09-30 9:54 ` Stefan G. Weichinger
2013-09-30 17:07 ` Volker Armin Hemmann
2013-09-30 17:36 ` Stefan G. Weichinger
2013-09-30 17:44 ` Bruce Hill
2013-09-30 17:46 ` Bruce Hill
2013-09-30 17:50 ` Stefan G. Weichinger
2013-09-30 18:23 ` Stefan G. Weichinger
2013-09-30 20:03 ` Stefan G. Weichinger
2013-10-01 8:26 ` Stefan G. Weichinger
2013-10-01 12:32 ` [gentoo-user] " Nicolas Sebrecht
2013-10-01 14:00 ` Stefan G. Weichinger
2013-10-01 19:21 ` Stefan G. Weichinger
2013-10-09 14:53 ` Stefan G. Weichinger
2013-10-09 18:20 ` Nicolas Sebrecht
2013-10-09 19:17 ` Stefan G. Weichinger
2013-10-09 19:57 ` Volker Armin Hemmann
2013-10-09 20:05 ` Stefan G. Weichinger
2013-10-09 20:40 ` Stefan G. Weichinger
2013-10-09 22:11 ` Stefan G. Weichinger
2013-10-09 22:18 ` Stefan G. Weichinger
2013-10-10 12:20 ` Bruce Hill
2013-10-10 14:38 ` Stefan G. Weichinger
2013-10-14 6:23 ` Stefan G. Weichinger
2013-10-14 17:21 ` Volker Armin Hemmann
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=52455F01.4060102@xunil.at \
--to=lists@xunil.at \
--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