From: Stefan Hrdlicka <s.hrdlicka@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH V2 pve-firewall 0/1] cache firewall/cluster.fw
Date: Fri, 25 Nov 2022 15:47:24 +0100 [thread overview]
Message-ID: <20221125144725.3231444-1-s.hrdlicka@proxmox.com> (raw)
This patch adds the firewall/cluster.fw to caching. On my system with a
list of 25k IP sets CPU consumption for the process went from ~20 % to
~10 % with this caching enabled. Still pretty high but better then
before.
V1 -> V2
# pve-firewall
* fix review issues
# pve-cluster
* already accepted
Stefan Hrdlicka (1):
fix #1965: cache firewall/cluster.fw file
src/PVE/Firewall.pm | 108 ++++++++++++++++++++++++++++++--------------
1 file changed, 75 insertions(+), 33 deletions(-)
--
2.30.2
next reply other threads:[~2022-11-25 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 14:47 Stefan Hrdlicka [this message]
2022-11-25 14:47 ` [pve-devel] [PATCH V2 pve-firewall 1/1] fix #1965: cache firewall/cluster.fw file Stefan Hrdlicka
2024-02-15 15:35 ` Lukas Wagner
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=20221125144725.3231444-1-s.hrdlicka@proxmox.com \
--to=s.hrdlicka@proxmox.com \
--cc=pve-devel@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