From: Stefan Radman via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Stefan Radman <stefan.radman@me.com>,
PVE User List <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] replication bandwith limit not respected
Date: Fri, 6 Sep 2024 20:18:20 +0300 [thread overview]
Message-ID: <mailman.93.1725643479.414.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <3ee95219-6894-4ff6-a89c-9e4a8d81b74d@suma-informatika.hr>
[-- Attachment #1: Type: message/rfc822, Size: 7563 bytes --]
From: Stefan Radman <stefan.radman@me.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: PVE User List <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] replication bandwith limit not respected
Date: Fri, 6 Sep 2024 20:18:20 +0300
Message-ID: <C89D18A7-57D5-4AF0-926D-A651237997AD@me.com>
Hi Tonči
I am not familiar with PVE storage replication but with networks.
Your answers to the questions below might help everyone on this list (including me) to better understand the issues behind the problem you are facing.
> lowered replication speed down to 80MB/s
Have you tried much lower rates (e.g. 10MB/s)?
Did anything change in the bandwidth utilization?
> replcation still uses whole NIC bandwith (1G)
How do you know?
How do know that storage replication cloggs your network and not some other apllication?
Where do you measure the replication traffic and how?
Are you running Jumbo frames (e.g. MTU 9000) between the replication targets or standard MTU 1500?
If you are not using a dedicated NIC for storage replication you are likely (and should be) running on standard MTU.
Using the standard MTU will generate more packets than jumbo frames, thus more headers, thus more overhead.
A bandwidth limit of 80MB/s translates to rougly 640Mbit/s but I assume that this does not include the overhead of protocols used by PVE storage replication (Ethernet, TCP/IP, SSH).
How much overhead in % do you expect?
My conservative assumption (rule of thumb) for SSH with standard MTU is 20% overhead.
That would be 768Mbit/s, leaving only 232Mbit/s for other traffic.
What is your output of “pveversion”?
Regards
Stefan
> On Sep 6, 2024, at 16:00, Tonči Stipičević <tonci@suma-informatika.hr> wrote:
>
> Hello,
>
> I'm running latest cluster (community support)
>
> And today I've lowered replication speed down to 80MB/s but replcation still uses whole NIC bandwith (1G) ... after few host restarts still the same
>
> 2024-09-06 14:37:31 using a bandwidth limit of 80000000 bytes per second for transferring 'data2:subvol-1007-disk-0'
>
> Does somebody else experience that too ?
>
>
> Thank you in advance
>
> BR
>
> Tonči
>
> --
> srdačan pozdrav / best regards
>
> Tonči Stipičević, dipl. ing. elektr.
> direktor / manager
>
> SUMA Informatika d.o.o., Badalićeva 27, OIB 93926415263
>
> Podrška / Upravljanje IT sustavima za male i srednje tvrtke
> Small & Medium Business IT Support / Management
>
> mob: 091 1234003
> www.suma-informatika.hr
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-09-06 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ee95219-6894-4ff6-a89c-9e4a8d81b74d@suma-informatika.hr>
2024-09-06 15:10 ` Stefan Nehlsen
2024-09-06 17:18 ` Stefan Radman via pve-user [this message]
2024-09-06 17:18 ` Stefan Radman via pve-user
[not found] <mailman.95.1725643774.414.pve-user@lists.proxmox.com>
2024-09-09 7:40 ` [PVE-User] pve-user Digest, Vol 198, Issue 6 Tonči Stipičević
2024-09-15 20:37 ` [PVE-User] replication bandwith limit not respected Stefan Radman via pve-user
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=mailman.93.1725643479.414.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=pve-user@pve.proxmox.com \
--cc=stefan.radman@me.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