From: dea <dea@corep.it>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Possible problem on NFS storage with release 2-3-3 (??)
Date: Tue, 14 Mar 2023 09:45:14 +0100 [thread overview]
Message-ID: <e9f18faf-d7d1-ba40-c517-b7902a669fee@corep.it> (raw)
In-Reply-To: <d18c1576-0eba-ee9c-281b-9b7e23ce1c89@proxmox.com>
Hi Thomas,
at the moment the PBS is using release 2.3-2 with kernel 6.1.10-1 and
everything is working properly, with the expected performance.
I too think the problem is not with PBS 2.3-3 but with the kernel, and
on my system kernel 6.1.10 runs really well.
The problem I have identified with kernel 5.15.85 is incredibly slow
performance on NFS storage.
3 days to finish a garbage collector on a 25 Tbyte SSD datastore (in
NFS) versus 3 hours now.
Yes, I think the best analysis is to upgrade to PBS 2.3-3 while keeping
the system running kernel 6.1.10.
I will let you know
Thank you very much
Luca
next prev parent reply other threads:[~2023-03-14 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 8:52 dea
2023-03-09 12:38 ` dea
2023-03-14 8:20 ` Thomas Lamprecht
2023-03-14 8:45 ` dea [this message]
2023-03-15 7:51 ` dea
2023-04-13 14:16 ` dea
2023-03-14 12:30 ` dea
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=e9f18faf-d7d1-ba40-c517-b7902a669fee@corep.it \
--to=dea@corep.it \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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