From: Gregor Burck <gregor@aeppelbroe.de>
To: pve-user@pve.proxmox.com
Subject: [PVE-User] ZFZ questions - performance and caching
Date: Mon, 29 Mar 2021 15:28:20 +0200 [thread overview]
Message-ID: <20210329152820.EGroupware._t1Sneg3e4BsuWUv_4EVNL7@heim.aeppelbroe.de> (raw)
Hi,
for calculating an backup server wich should be in worst case
additionaly an virtualisation server we thougth about a setup with
HDDs and for ZFZ chaching NVMes.
We plan all with enterprise products,...
I guess following Setup:
A 12 3,5 '' bay Server, 6 PVEe sockets, maybee with an 2,5'' Rear
entension kit for the OS
Backup envirement:
4 (or6) HDDs, 6 (or 8) TB without chaching
For virtualisation enviroment:
4 (or6) HDDs, 6 (or 8) TB with NVMe chaching
I think, for the backup enviroment there shouldn't be a chaching
neccessary, cause here is the network the limitation.
The VE part should be a little performer, but how big should the NVMe
cache? As I read, it is for the ZFZ log.
And how much is the performance increasemnt?
Bye
Gregor
next reply other threads:[~2021-03-29 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 13:28 Gregor Burck [this message]
2021-03-29 14:26 ` Gregor Burck
2021-03-30 7:34 ` Mikhail
2021-03-30 9:34 ` Gregor Burck
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=20210329152820.EGroupware._t1Sneg3e4BsuWUv_4EVNL7@heim.aeppelbroe.de \
--to=gregor@aeppelbroe.de \
--cc=pve-user@pve.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