From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] The low network throughput obsered on Open vSwitch bridge.
Date: Mon, 15 Mar 2021 12:37:57 +0800 [thread overview]
Message-ID: <CAGP6POKQVu6sBhWbRRa4qmiZYxakLRaOwJLT8881TF3PFWQxwQ@mail.gmail.com> (raw)
In-Reply-To: <67f6fcec-ae6b-2ebe-a104-84f4c2a6008f@gmail.com>
On Mon, Mar 15, 2021 at 12:00 PM Dmitry Petuhov <mityapetuhov@gmail.com> wrote:
>
> Hello.
>
> That's how TCP throughput mediation works. In basic case, you cannot
> canot fully saturate link by two opposite TCP connections regardless of
> using Open vSwitch.
>
> There's one dirty hack that can override this behavior: you could use
> qdisc on interface that prioritize packets that have ACK bit set over
> those that don't in same connection. It will saturate link, but may lead
> to other issues on certain types of traffic (because of packet
> reordering), so [almost] nobody use it in real life.
>
> Multiple parallel connections in same direction also saturate link more
> evenly.
Thanks a lot for your help and explanation. But I still can't
understand why the speed observed from pve (192.168.10.254) to another
physical machine (192.168.10.100) is always higher than that observed
in the reverse direction. Any hints for this phenomenon?
Regards
--
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Polytechnic University of Science and Technology engineering
NO. 552 North Gangtie Road, Xingtai, China
prev parent reply other threads:[~2021-03-15 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 3:33 Hongyi Zhao
2021-03-15 4:00 ` Dmitry Petuhov
2021-03-15 4:37 ` Hongyi Zhao [this message]
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=CAGP6POKQVu6sBhWbRRa4qmiZYxakLRaOwJLT8881TF3PFWQxwQ@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=pve-user@lists.proxmox.com \
/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