From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pbs-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
by lore.proxmox.com (Postfix) with ESMTPS id EFDE21FF185
for <inbox@lore.proxmox.com>; Mon, 23 Jun 2025 14:45:58 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id BB70211F89;
Mon, 23 Jun 2025 14:46:31 +0200 (CEST)
From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Date: Mon, 23 Jun 2025 14:45:43 +0200
Message-ID: <20250623124543.590388-1-c.ebner@proxmox.com>
X-Mailer: git-send-email 2.47.2
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.036 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DMARC_MISSING 0.1 Missing DMARC policy
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
Subject: [pbs-devel] [PATCH] docs: rephrase and extend rate limiting
description for sync jobs
X-BeenThere: pbs-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox Backup Server development discussion
<pbs-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pbs-devel>,
<mailto:pbs-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pbs-devel/>
List-Post: <mailto:pbs-devel@lists.proxmox.com>
List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel>,
<mailto:pbs-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pbs-devel-bounces@lists.proxmox.com
Sender: "pbs-devel" <pbs-devel-bounces@lists.proxmox.com>
Since commit 37a85cf6 ("fix: ui: sync job: edit rate limit based on
sync direction") rate limits for sync jobs can be correctly applied
for both directions. State this in the documentation and explicitley
mention the directions to reduce confusion.
Further, also mention the burst parameters, as they are not mentioned
at all.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
While the initial request in the community forum asked for improved
documentation of the configuration file's parameters [0], this is
currently not possible without explicitley defining new types for
each as autogenerated for the api schema, which defines these values
as `HumanByte` and a description cannot be set for external types.
This patch tries to improve the discoverability for the rate and
burst parameters for both the sync and general traffic limits.
[0] https://forum.proxmox.com/threads/167738/
docs/managing-remotes.rst | 4 +++-
docs/traffic-control.rst | 9 +++++----
2 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/docs/managing-remotes.rst b/docs/managing-remotes.rst
index da1d53cbd..ddbe3e9b6 100644
--- a/docs/managing-remotes.rst
+++ b/docs/managing-remotes.rst
@@ -239,7 +239,9 @@ command-line tool:
# proxmox-backup-manager sync-job update ID --rate-in 20MiB
-For sync jobs in push direction use the ``rate-out`` option instead.
+For sync jobs in push direction use the ``rate-out`` option instead. To allow
+for traffic bursts, you can set the size of the token bucket filter used for
+traffic limiting via ``burst-in`` or ``burst-out`` parameters.
Sync Direction Push
^^^^^^^^^^^^^^^^^^^
diff --git a/docs/traffic-control.rst b/docs/traffic-control.rst
index 7cfd2d16b..bd370e804 100644
--- a/docs/traffic-control.rst
+++ b/docs/traffic-control.rst
@@ -19,11 +19,12 @@ certain hosts.
You can manage the traffic controls either via the web-interface or using the
``traffic-control`` commands of the ``proxmox-backup-manager`` command-line
-tool.
+tool. Traffic is limited by rate (``rate-in`` and ``rate-out``) and allows for
+short bursts by setting the token bucket size (``burst-in`` and ``burst-out``).
-.. note:: Sync jobs on the server are not affected by the configured rate-in limits.
- If you want to limit the incoming traffic that a pull-based sync job
- generates, you need to setup a job-specific rate-in limit. See
+.. note:: Sync jobs on the server are not affected by the configured rate limits.
+ If you want to limit the incoming traffic of pull-based or outgoing traffic
+ of push-based sync job, you need to setup a job-specific rate-in limit. See
:ref:`syncjobs`.
The following command adds a traffic control rule to limit all IPv4 clients
--
2.47.2
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# Date: Mon Jun 23 14:12:00 2025 +0200
#
# On branch improve-sync-rate-docs
# Changes to be committed:
# modified: docs/managing-remotes.rst
# modified: docs/traffic-control.rst
#
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel