Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #207240
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: putty go slow |
| Date | 2019-04-10 15:40 +0200 |
| Message-ID | <xLlCh-21N-3@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <xKSJX-GT-1@gated-at.bofh.it> <xKWNz-3m0-1@gated-at.bofh.it> <xLil4-9e-9@gated-at.bofh.it> <xLkdb-1ib-1@gated-at.bofh.it> <xLl9f-1S1-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Apr 10, 2019 at 03:01:51PM +0200, Peter Wiersig wrote: >I strive for local networks that would have single digit drops in 47m >packets and I'm willing to spend the money for the equipment to achieve >that. My quoted ifconfig output comes from a rented server in some >datacenter where I don't have the power to choose anything HW related >apart from my price point for the server cost, and they almost reach my >goal in error counters. I have no idea how critical micks hardware is >and what budget choices he makes. A drop in that output indicates that the packet was lost on the local machine. It's not a hardware issue on the network so changing out pieces of the network isn't going to change it. If it was a higher percentage I'd look at whether a NIC with better offload was warranted, or a CPU upgrade, or whether the system was running network-related software that could be upgraded to something more efficient, etc. There's more debugging that could be done if needed, but for .01% I'd write it off as a momentary blip, maybe related to load during startup of a network service, and ignore it unless it started growing. Mike Stone
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
putty go slow mick crane <mick.crane@gmail.com> - 2019-04-08 22:40 +0200
Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-09 00:00 +0200
Re: putty go slow lev@levlaz.org - 2019-04-09 00:10 +0200
Re: putty go slow mick crane <mick.crane@gmail.com> - 2019-04-09 00:40 +0200
Re: putty go slow lev@levlaz.org - 2019-04-09 06:00 +0200
Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-09 08:50 +0200
Re: putty go slow mick crane <mick.crane@gmail.com> - 2019-04-09 13:10 +0200
Re: putty go slow Dan Ritter <dsr@randomstring.org> - 2019-04-09 13:20 +0200
Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 12:10 +0200
Re: putty go slow Michael Stone <mstone@debian.org> - 2019-04-10 14:10 +0200
Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 15:10 +0200
Re: putty go slow mick crane <mick.crane@gmail.com> - 2019-04-10 15:30 +0200
Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 16:10 +0200
Re: putty go slow Michael Stone <mstone@debian.org> - 2019-04-10 15:40 +0200
Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 16:40 +0200
Re: putty go slow rhkramer@gmail.com - 2019-04-10 16:20 +0200
Re: putty go slow rhkramer@gmail.com - 2019-04-10 16:30 +0200
Re: putty go slow rhkramer@gmail.com - 2019-04-12 14:50 +0200
Re: putty go slow Michael Stone <mstone@debian.org> - 2019-04-10 17:20 +0200
Re: putty go slow Celejar <celejar@gmail.com> - 2019-04-09 19:50 +0200
csiph-web