From: "Mark Schouten" <mark@tuxis.nl>
To: Roland <devzero@web.de>,
"Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>,
"Thomas Lamprecht" <t.lamprecht@proxmox.com>
Subject: Re: [pbs-devel] Slow overview of existing backups
Date: Mon, 13 Mar 2023 12:48:24 +0000 [thread overview]
Message-ID: <ema2a35a81-c3a7-4144-808b-5b9e37b47607@eb9993ff.com> (raw)
In-Reply-To: <em642f905f-1401-4faa-b066-bce5e5e713bf@eb9993ff.com>
So, setting primarycache to metadata does not help. Maybe even makes the
overview worse.
Requesting one specific customer takes 55 seconds. This is a datastore
with 334 groups and 2991 snapshots (About 53TB of total data in this
datastore).
—
Mark Schouten, CTO
Tuxis B.V.
mark@tuxis.nl / +31 318 200208
------ Original Message ------
From "Mark Schouten" <mark@tuxis.nl>
To "Roland" <devzero@web.de>; "Proxmox Backup Server development
discussion" <pbs-devel@lists.proxmox.com>; "Thomas Lamprecht"
<t.lamprecht@proxmox.com>
Date 3/10/2023 11:52:37 AM
Subject Re[2]: [pbs-devel] Slow overview of existing backups
>Hi,
>
>> >- 2 three-way mirrors of 960GB Samsung PM9A3 nvme’s as special devices
>>
>>ah ok, i see you should have fast metadata access because of special device
>>
>
>That’s what I would expect yes. But maybe I can try to set primarycache to metadata, not sure if that would have a negative impact on prefetching though..
>
>>what about freshly booting your backup server and issuing
>>
>>zpool iostat -rv
>>
>>after listing backups and observing slowness ?
>
>There are too many clusters connected to this machine to make it ’silent’ for a while and debugging this.
>
>—
>Mark Schouten, CTO
>Tuxis B.V.
>mark@tuxis.nl / +31 318 200208
next prev parent reply other threads:[~2023-03-13 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 10:26 Mark Schouten
2023-01-25 16:08 ` Thomas Lamprecht
2023-01-26 8:03 ` Mark Schouten
2023-03-10 9:09 ` Mark Schouten
2023-03-10 10:16 ` Roland
2023-03-10 10:52 ` Mark Schouten
2023-03-13 12:48 ` Mark Schouten [this message]
2023-03-10 10:02 ` Roland
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=ema2a35a81-c3a7-4144-808b-5b9e37b47607@eb9993ff.com \
--to=mark@tuxis.nl \
--cc=devzero@web.de \
--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