How fast is your backup datastore? Benchmark tool

joace

Member
Nov 4, 2014
13
0
21
Here is my benchmark on newly setup PBS (test locally on the datastores)
PBS config (on a HPE DL380 Gen10 unit):
  • Xeon Gold 5117 14c/28t 2.00GHz x 2
  • 128GB DDR4 RDIMM 2400MHz
  • 2 datastores:
    • SAS SSD 1.6TB x 16 (8 mirror vdev, this will be official datastore for backup)
    • NVMe 960GB x 2 in mirror (for testing purpose)
Benchmark result:
  • On SAS SSD datastore
Uploaded 935 chunks in 5 seconds.
Time per request: 5372 microseconds.
TLS speed: 780.75 MB/s
SHA256 speed: 360.64 MB/s
Compression speed: 365.17 MB/s
Decompress speed: 484.88 MB/s
AES256/GCM speed: 1054.89 MB/s
Verify speed: 206.40 MB/s
┌───────────────────────────────────┬────────────────────┐
│ Name │ Value │
╞═══════════════════════════════════╪════════════════════╡
│ TLS (maximal backup upload speed) │ 780.75 MB/s (63%) │
├───────────────────────────────────┼────────────────────┤
│ SHA256 checksum computation speed │ 360.64 MB/s (18%) │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 compression speed │ 365.17 MB/s (49%) │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 decompression speed │ 484.88 MB/s (40%) │
├───────────────────────────────────┼────────────────────┤
│ Chunk verification speed │ 206.40 MB/s (27%) │
├───────────────────────────────────┼────────────────────┤
│ AES256 GCM encryption speed │ 1054.89 MB/s (29%) │
└───────────────────────────────────┴────────────────────┘

  • On NVMe datastore
Uploaded 908 chunks in 5 seconds.
Time per request: 5514 microseconds.
TLS speed: 760.56 MB/s
SHA256 speed: 360.83 MB/s
Compression speed: 367.37 MB/s
Decompress speed: 482.57 MB/s
AES256/GCM speed: 1058.30 MB/s
Verify speed: 206.64 MB/s
┌───────────────────────────────────┬────────────────────┐
│ Name │ Value │
╞═══════════════════════════════════╪════════════════════╡
│ TLS (maximal backup upload speed) │ 760.56 MB/s (62%) │
├───────────────────────────────────┼────────────────────┤
│ SHA256 checksum computation speed │ 360.83 MB/s (18%) │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 compression speed │ 367.37 MB/s (49%) │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 decompression speed │ 482.57 MB/s (40%) │
├───────────────────────────────────┼────────────────────┤
│ Chunk verification speed │ 206.64 MB/s (27%) │
├───────────────────────────────────┼────────────────────┤
│ AES256 GCM encryption speed │ 1058.30 MB/s (29%) │
└───────────────────────────────────┴────────────────────┘

Seems both are not getting nice number with these SSD drives, especially for NVMe datastore like other guys posted result here, not sure whether this is because of low processor speed, and whether PBS is single thread, so dual socket is not really helpful here. Can anybody share some ideas to help me improve the performance? Thanks!
 

Toranaga

Active Member
Jun 17, 2017
60
9
28
55
Not fast, but working:

Supermicro X11SBA-LN4F, Intel N3700, 16GB, WD RED Pro 14 TB, PBS Datastore ZFS on luks

Uploaded 52 chunks in 5 seconds.
Time per request: 111703 microseconds.
TLS speed: 37.55 MB/s
SHA256 speed: 243.08 MB/s
Compression speed: 221.92 MB/s
Decompress speed: 291.81 MB/s
AES256/GCM speed: 745.87 MB/s
Verify speed: 125.93 MB/s
┌───────────────────────────────────┬───────────────────┐
│ Name │ Value │
╞═══════════════════════════════════╪═══════════════════╡
│ TLS (maximal backup upload speed) │ 37.55 MB/s (3%) │
├───────────────────────────────────┼───────────────────┤
│ SHA256 checksum computation speed │ 243.08 MB/s (12%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 compression speed │ 221.92 MB/s (30%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 decompression speed │ 291.81 MB/s (24%) │
├───────────────────────────────────┼───────────────────┤
│ Chunk verification speed │ 125.93 MB/s (17%) │
├───────────────────────────────────┼───────────────────┤
│ AES256 GCM encryption speed │ 745.87 MB/s (20%) │
└───────────────────────────────────┴───────────────────┘
 
Last edited:

Toranaga

Active Member
Jun 17, 2017
60
9
28
55
No, as far as I know is zfs not full crypted, some data stay uncrypted.
So I do not use the crypt part of zfs.
 

Dunuin

Famous Member
Jun 30, 2020
8,924
2,281
156
Germany
No, as far as I know is zfs not full crypted, some data stay uncrypted.
So I do not use the crypt part of zfs.
Jup, still the question why you don't simple use the encryption that PBS offers on the software level. Then you don't need t encrypt you filesystems.
 
  • Like
Reactions: Felix.

Toranaga

Active Member
Jun 17, 2017
60
9
28
55
I use the target disk for more than pbs
1. The disk is used as rsync target for backups that run to long to do it with pbs. These data needs to be crypted too.
2. The disk is datastore for the emergency pve installed parallel to the pbs, thats the reason for zfs instead of lvm.
3. I see problems with the crash recovery if the pve is complete gone? where are the keys to restore the vms? Maybe incomplete informations on my side. The passphrase of luks is entered by hand on boot, this works for me. Crash recovery needs only the pure disk with the datastore of the pbs.
 
Last edited:

Dunuin

Famous Member
Jun 30, 2020
8,924
2,281
156
Germany
3. I see problems with the crash recovery if the pve is complete gone? where are the keys to restore the vms? Maybe incomplete informations on my side. The passphrase of luks is entered by hand on boot, this works for me. Crash recovery needs only the pure disk with the datastore of the pbs.
You save the key when enabling encryption for the PBS datastore.
 

Felix.

Active Member
May 13, 2018
154
18
38
22
I use the target disk for more than pbs
1. The disk is used as rsync target for backups that run to long to do it with pbs. These data needs to be crypted too.
2. The disk is datastore for the emergency pve installed parallel to the pbs, thats the reason for zfs instead of lvm.
3. I see problems with the crash recovery if the pve is complete gone? where are the keys to restore the vms? Maybe incomplete informations on my side. The passphrase of luks is entered by hand on boot, this works for me. Crash recovery needs only the pure disk with the datastore of the pbs.
If you did not download it from the UI, you can find the keys in /etc/pve/priv/storage.
Also you can enable the Master Key Feature, that way you only need to keep eyes on a single keypair: https://pve.proxmox.com/wiki/Storage:_Proxmox_Backup_Server#storage_pbs_encryption
 

Robstarusa

Active Member
Feb 19, 2009
80
3
28
Backup server is E3-1240v3 with 32G ram & sata ssds on 10Gbit/s Ethernet
VM Host is 5950x with 2.5Gbit/s ethernet & 3.84TB nvme ssd.

My biggest issue is occasional full verifies where the e3-1243v3 cpu goes to 400% for hours at a time. Typically 4-5 Hours.

Benchmark run from VM Host:

Uploaded 355 chunks in 5 seconds.
Time per request: 14438 microseconds.
TLS speed: 290.49 MB/s
SHA256 speed: 2397.32 MB/s
Compression speed: 924.12 MB/s
Decompress speed: 1209.97 MB/s
AES256/GCM speed: 2856.40 MB/s
Verify speed: 803.62 MB/s

┌───────────────────────────────────┬─────────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪═════════════════════╡ │ TLS (maximal backup upload speed) │ 290.49 MB/s (24%) │ ├───────────────────────────────────┼─────────────────────┤ │ SHA256 checksum computation speed │ 2397.32 MB/s (119%) │ ├───────────────────────────────────┼─────────────────────┤ │ ZStd level 1 compression speed │ 924.12 MB/s (123%) │ ├───────────────────────────────────┼─────────────────────┤ │ ZStd level 1 decompression speed │ 1209.97 MB/s (101%) │ ├───────────────────────────────────┼─────────────────────┤ │ Chunk verification speed │ 803.62 MB/s (106%) │ ├───────────────────────────────────┼─────────────────────┤ │ AES256 GCM encryption speed │ 2856.40 MB/s (78%) │ └───────────────────────────────────┴─────────────────────┘
 

semihtore

New Member
May 16, 2022
7
1
1
32
IST,Turkey
www.semihbilisim.com
Hi.

Help mee!!!!

very very very slow speed backup

I have 10Gb ethernet and 8Gb SAN Switch

Uploaded 43 chunks in 6 seconds.
Time per request: 159704 microseconds.
TLS speed: 26.26 MB/s
SHA256 speed: 215.65 MB/s
Compression speed: 268.07 MB/s
Decompress speed: 395.54 MB/s
AES256/GCM speed: 588.19 MB/s
Verify speed: 138.26 MB/s
┌───────────────────────────────────┬───────────────────┐
│ Name │ Value │
╞═══════════════════════════════════╪═══════════════════╡
│ TLS (maximal backup upload speed) │ 26.26 MB/s (2%) │
├───────────────────────────────────┼───────────────────┤
│ SHA256 checksum computation speed │ 215.65 MB/s (11%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 compression speed │ 268.07 MB/s (36%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 decompression speed │ 395.54 MB/s (33%) │
├───────────────────────────────────┼───────────────────┤
│ Chunk verification speed │ 138.26 MB/s (18%) │
├───────────────────────────────────┼───────────────────┤
│ AES256 GCM encryption speed │ 588.19 MB/s (16%) │
└───────────────────────────────────┴───────────────────┘


And local disk performance for NFS : 260 MiB/s

please help me!!
 

liberodark

Member
Apr 26, 2021
83
19
8
30
Result with a PBS VM

4x Cores
8 Go Ram
ZFS HDD (SATA Storage via Netapp NFS v3)


On PBS :

Code:
proxmox-backup-client benchmark --repository backup_c
Password for "root@pam": *****************
Uploaded 498 chunks in 5 seconds.
Time per request: 10073 microseconds.
TLS speed: 416.35 MB/s
SHA256 speed: 330.75 MB/s
Compression speed: 227.08 MB/s
Decompress speed: 270.28 MB/s
AES256/GCM speed: 530.00 MB/s
Verify speed: 147.19 MB/s
┌───────────────────────────────────┬───────────────────┐
│ Name                              │ Value             │
╞═══════════════════════════════════╪═══════════════════╡
│ TLS (maximal backup upload speed) │ 416.35 MB/s (34%) │
├───────────────────────────────────┼───────────────────┤
│ SHA256 checksum computation speed │ 330.75 MB/s (16%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 compression speed    │ 227.08 MB/s (30%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 decompression speed  │ 270.28 MB/s (23%) │
├───────────────────────────────────┼───────────────────┤
│ Chunk verification speed          │ 147.19 MB/s (19%) │
├───────────────────────────────────┼───────────────────┤
│ AES256 GCM encryption speed       │ 530.00 MB/s (15%) │
└───────────────────────────────────┴───────────────────┘

On PVE :

Code:
proxmox-backup-client benchmark --repository root@pam@my_ip:backup_c
Password for "root@pam": *****************
Uploaded 148 chunks in 5 seconds.
Time per request: 35880 microseconds.
TLS speed: 116.90 MB/s
SHA256 speed: 306.85 MB/s
Compression speed: 307.21 MB/s
Decompress speed: 480.33 MB/s
AES256/GCM speed: 934.35 MB/s
Verify speed: 185.04 MB/s
┌───────────────────────────────────┬───────────────────┐
│ Name                              │ Value             │
╞═══════════════════════════════════╪═══════════════════╡
│ TLS (maximal backup upload speed) │ 116.90 MB/s (9%)  │
├───────────────────────────────────┼───────────────────┤
│ SHA256 checksum computation speed │ 306.85 MB/s (15%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 compression speed    │ 307.21 MB/s (41%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 decompression speed  │ 480.33 MB/s (40%) │
├───────────────────────────────────┼───────────────────┤
│ Chunk verification speed          │ 185.04 MB/s (24%) │
├───────────────────────────────────┼───────────────────┤
│ AES256 GCM encryption speed       │ 934.35 MB/s (26%) │
└───────────────────────────────────┴───────────────────┘
 
Last edited:
Oct 7, 2019
203
51
33
Hello,

I'm getting these numbers from a AMD Ryzen 7 PRO 3700 8-Core Processor:

Code:
SHA256 speed: 2114.85 MB/s
Compression speed: 593.17 MB/s
Decompress speed: 796.48 MB/s
AES256/GCM speed: 1866.55 MB/s
Verify speed: 588.18 MB/s
┌───────────────────────────────────┬─────────────────────┐
│ Name                              │ Value               │
╞═══════════════════════════════════╪═════════════════════╡
│ TLS (maximal backup upload speed) │ not tested          │
├───────────────────────────────────┼─────────────────────┤
│ SHA256 checksum computation speed │ 2114.85 MB/s (105%) │
├───────────────────────────────────┼─────────────────────┤
│ ZStd level 1 compression speed    │ 593.17 MB/s (79%)   │
├───────────────────────────────────┼─────────────────────┤
│ ZStd level 1 decompression speed  │ 796.48 MB/s (66%)   │
├───────────────────────────────────┼─────────────────────┤
│ Chunk verification speed          │ 588.18 MB/s (78%)   │
├───────────────────────────────────┼─────────────────────┤
│ AES256 GCM encryption speed       │ 1866.55 MB/s (51%)  │
└───────────────────────────────────┴─────────────────────┘

I know that the "PRO" version is somewhat slower than the standard 3700x, but still these numbers seem to be too low, specially compared with the ones provided in the wiki: https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#AMD_Ryzen_7_3700X_8-Core_Processor

This server has a standalone PVE running a couple of very lightweight VMs (linux nameservers) and installed PBS alongside PVE. Anyone else have any data using Ryzen 7 CPUs? I would like to get some more numbers before I dwelve into the BIOS and other settings which may affect the performance.

Thanks!
 

Neobin

Famous Member
Apr 29, 2021
1,101
387
83
PBS: 2.2.7
Kernel: 5.19

AMD Ryzen 9 5950X:
Code:
┌───────────────────────────────────┬─────────────────────┐
│ Name                              │ Value               │
╞═══════════════════════════════════╪═════════════════════╡
│ TLS (maximal backup upload speed) │ not tested          │
├───────────────────────────────────┼─────────────────────┤
│ SHA256 checksum computation speed │ 2454.96 MB/s (121%) │
├───────────────────────────────────┼─────────────────────┤
│ ZStd level 1 compression speed    │ 924.92 MB/s (123%)  │
├───────────────────────────────────┼─────────────────────┤
│ ZStd level 1 decompression speed  │ 1203.11 MB/s (100%) │
├───────────────────────────────────┼─────────────────────┤
│ Chunk verification speed          │ 793.16 MB/s (105%)  │
├───────────────────────────────────┼─────────────────────┤
│ AES256 GCM encryption speed       │ 2813.84 MB/s (77%)  │
└───────────────────────────────────┴─────────────────────┘

AMD Ryzen 7 5700G:
Code:
┌───────────────────────────────────┬─────────────────────┐
│ Name                              │ Value               │
╞═══════════════════════════════════╪═════════════════════╡
│ TLS (maximal backup upload speed) │ not tested          │
├───────────────────────────────────┼─────────────────────┤
│ SHA256 checksum computation speed │ 2268.14 MB/s (112%) │
├───────────────────────────────────┼─────────────────────┤
│ ZStd level 1 compression speed    │ 898.85 MB/s (120%)  │
├───────────────────────────────────┼─────────────────────┤
│ ZStd level 1 decompression speed  │ 1147.84 MB/s (96%)  │
├───────────────────────────────────┼─────────────────────┤
│ Chunk verification speed          │ 773.07 MB/s (102%)  │
├───────────────────────────────────┼─────────────────────┤
│ AES256 GCM encryption speed       │ 2704.96 MB/s (74%)  │
└───────────────────────────────────┴─────────────────────┘

Intel Core i9-9900K:
Code:
┌───────────────────────────────────┬────────────────────┐
│ Name                              │ Value              │
╞═══════════════════════════════════╪════════════════════╡
│ TLS (maximal backup upload speed) │ not tested         │
├───────────────────────────────────┼────────────────────┤
│ SHA256 checksum computation speed │ 648.44 MB/s (32%)  │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 compression speed    │ 690.37 MB/s (92%)  │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 decompression speed  │ 940.24 MB/s (78%)  │
├───────────────────────────────────┼────────────────────┤
│ Chunk verification speed          │ 381.77 MB/s (50%)  │
├───────────────────────────────────┼────────────────────┤
│ AES256 GCM encryption speed       │ 2017.46 MB/s (55%) │
└───────────────────────────────────┴────────────────────┘

Intel Atom C2558:
Code:
┌───────────────────────────────────┬───────────────────┐
│ Name                              │ Value             │
╞═══════════════════════════════════╪═══════════════════╡
│ TLS (maximal backup upload speed) │ not tested        │
├───────────────────────────────────┼───────────────────┤
│ SHA256 checksum computation speed │ 116.25 MB/s (6%)  │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 compression speed    │ 144.09 MB/s (19%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 decompression speed  │ 178.57 MB/s (15%) │
├───────────────────────────────────┼───────────────────┤
│ Chunk verification speed          │ 69.40 MB/s (9%)   │
├───────────────────────────────────┼───────────────────┤
│ AES256 GCM encryption speed       │ 215.83 MB/s (6%)  │
└───────────────────────────────────┴───────────────────┘
 

ITT

Active Member
Mar 19, 2021
335
79
28
42
Xeon E3 1231 v3 / 32GB Ram, SSD


Schedutil:

Code:
Uploaded 936 chunks in 5 seconds.
Time per request: 5378 microseconds.
TLS speed: 779.85 MB/s
SHA256 speed: 444.46 MB/s
Compression speed: 434.62 MB/s
Decompress speed: 671.52 MB/s
AES256/GCM speed: 1268.67 MB/s
Verify speed: 264.32 MB/s
┌───────────────────────────────────┬────────────────────┐
│ Name                              │ Value              │
╞═══════════════════════════════════╪════════════════════╡
│ TLS (maximal backup upload speed) │ 779.85 MB/s (63%)  │
├───────────────────────────────────┼────────────────────┤
│ SHA256 checksum computation speed │ 444.46 MB/s (22%)  │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 compression speed    │ 434.62 MB/s (58%)  │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 decompression speed  │ 671.52 MB/s (56%)  │
├───────────────────────────────────┼────────────────────┤
│ Chunk verification speed          │ 264.32 MB/s (35%)  │
├───────────────────────────────────┼────────────────────┤
│ AES256 GCM encryption speed       │ 1268.67 MB/s (35%) │
└───────────────────────────────────┴────────────────────┘
After some time, same Hardware but switched to acpi_cpufreq:

Code:
Uploaded 1026 chunks in 5 seconds.
Time per request: 4884 microseconds.
TLS speed: 858.73 MB/s
SHA256 speed: 482.43 MB/s
Compression speed: 513.00 MB/s
Decompress speed: 819.40 MB/s
AES256/GCM speed: 1600.68 MB/s
Verify speed: 302.91 MB/s
┌───────────────────────────────────┬────────────────────┐
│ Name                              │ Value              │
╞═══════════════════════════════════╪════════════════════╡
│ TLS (maximal backup upload speed) │ 858.73 MB/s (70%)  │
├───────────────────────────────────┼────────────────────┤
│ SHA256 checksum computation speed │ 482.43 MB/s (24%)  │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 compression speed    │ 513.00 MB/s (68%)  │
├───────────────────────────────────┼────────────────────┤
│ ZStd level 1 decompression speed  │ 819.40 MB/s (68%)  │
├───────────────────────────────────┼────────────────────┤
│ Chunk verification speed          │ 302.91 MB/s (40%)  │
├───────────────────────────────────┼────────────────────┤
│ AES256 GCM encryption speed       │ 1600.68 MB/s (44%) │
└───────────────────────────────────┴────────────────────┘

I think Uploaded xxx chunks in 5 seconds. is very important (Disk-/Wirespeed)
 
Last edited:

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,547
1,817
174
South Tyrol/Italy
shop.proxmox.com
I think Uploaded xxx chunks in 5 seconds. is very important (Disk-/Wirespeed)
It's also quite dependent of few other factors, especially connection latency and throughput can have a big impact; network throughput is the obvious upper limit independent on how much IO both ends can handle, and high-latencies can have a much higher impact than one might expect (keyword: TCP head of line blocking).
 
  • Like
Reactions: ITT

Neobin

Famous Member
Apr 29, 2021
1,101
387
83
Out of curiosity, I tested the Intel Core i9-9900K again with: mitigations=off:

Intel Core i9-9900KWiki referenceDefault mitigationsMitigations = off
PBS1.0.82.2.72.2.7
Kernel5.45.195.19
TLS (maximal backup upload speed)not testednot testednot tested
SHA256 checksum computation speed612.84 MB/s (30%)648.44 MB/s (32%)648.85 MB/s (32%)
ZStd level 1 compression speed694.92 MB/s (92%)690.37 MB/s (92%)775.14 MB/s (103%)
ZStd level 1 decompression speed1518.13 MB/s (127%)940.24 MB/s (78%)1149.87 MB/s (96%)
Chunk verification speed438.38 MB/s (58%)381.77 MB/s (50%)413.62 MB/s (55%)
AES256 GCM encryption speed4099.33 MB/s (112%)2017.46 MB/s (55%)2537.91 MB/s (70%)

Mitigations output from: lscpu:

Intel Core i9-9900KDefault mitigationsMitigations = off
Vulnerability Itlb multihitKVM: Mitigation: Split huge pagesKVM: Vulnerable
Vulnerability L1tfNot affectedNot affected
Vulnerability MdsMitigation; Clear CPU buffers; SMT vulnerableVulnerable; SMT vulnerable
Vulnerability MeltdownNot affectedNot affected
Vulnerability Mmio stale dataMitigation; Clear CPU buffers; SMT vulnerableVulnerable
Vulnerability RetbleedMitigation; IBRSVulnerable
Vulnerability Spec store bypassMitigation; Speculative Store Bypass disabled via prctlVulnerable
Vulnerability Spectre v1Mitigation; usercopy/swapgs barriers and __user pointer sanitizationVulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers
Vulnerability Spectre v2Mitigation; IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affectedVulnerable, IBPB: disabled, STIBP: disabled, PBRSB-eIBRS: Not affected
Vulnerability SrbdsMitigation; MicrocodeVulnerable
Vulnerability Tsx async abortMitigation; TSX disabledMitigation; TSX disabled

I am wondering, where the rather big difference for the "ZStd level 1 decompression speed" and especially the massive difference for the "AES256 GCM encryption speed" even with: mitigations=off compared to the wiki reference: [1] does come from.
@t.lamprecht: Could this be explained with changes made between the PBS- and/or kernel-versions?
One thing I could think of hardware-wise: Are those tests heavily RAM sensitive? Because the RAM in this machine runs at the CPU's official supported default/max speed of only 2666 MHz and if the reference machine from the wiki would have run with e.g.: 3200 MHz RAM, this might explain it? But would this really be such a massive difference in regard of the "AES256 GCM encryption speed"?
Not that I want to dig too deep in this, but a difference between ~4100 MB/s and ~2000/~2500 MB/s makes me a bit curious. :D

[1] https://pve.proxmox.com/wiki/PBS_Cl....28R.29_Core.28TM.29_i9-9900K_CPU_.40_3.60GHz
 
  • Like
Reactions: Dunuin and ITT

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!