From: Stefan Nehlsen <sn@ltsh.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] replication bandwith limit not respected
Date: Fri, 6 Sep 2024 17:10:54 +0200 [thread overview]
Message-ID: <a5afd574-a7f3-4e53-aa2a-cf34be71f488@ltsh.de> (raw)
In-Reply-To: <3ee95219-6894-4ff6-a89c-9e4a8d81b74d@suma-informatika.hr>
Am 06.09.24 um 15:00 schrieb Tonči Stipičević:
> Hello,
>
> I'm running latest cluster (community support)
A little more information about your cluster might help.
> 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 ?
Nowadays everything will be able to saturize 1Gbps links.
Better you add faster hardware to your cluster.
Cheapest solution will be connecting 2 nodes directly with 2 USB3
ethernet devices and a cable. 2.5 or 5 Gbps just for cluster
communication or/and replication will make a difference.
10Gbps cards and switches wound be even better.
Dual 40 Gbps connections probably may be overkill :-)
It all depends on what you are doing.
Stefan
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next parent reply other threads:[~2024-09-06 15:16 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 [this message]
2024-09-06 17:18 ` Stefan Radman via pve-user
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=a5afd574-a7f3-4e53-aa2a-cf34be71f488@ltsh.de \
--to=sn@ltsh.de \
--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