

│ ZStd level 1 compression speed │ 406.54 MB/s (54%) │ │ SHA256 checksum computation speed │ 407.06 MB/s (20%) │ │ TLS (maximal backup upload speed) │ not tested │ PBS Client Benchmark SHA256 speed: 407.06 MB/s
#CPU BENCHMARK COMPARISON 2019 UPDATE#
The quite modern Ryzen 7 5800X beats the Raspberry Pi 4's Cortex-A72 CPU by a factor of 16.5 (1655 % faster).įor the PBS build more core help first, but at the end linking (which makes out a significant part of the total build time) is done in a single process, so one needs all three, high core count, high clock rate and high instructions per cycle rate to "win" here.ĭata Intel(R) Xeon(R) CPU E5-2620 v3 2.40GHz Update date Note that Watt/Cores was chosen as just comparing TDP makes one draw conclusions which will be wrong in real world - as the benchmark is mostly single core, and thus multicore systems look worse than they will in practice (where multiple backup jobs/verifications/GCs/. A few points more or less may not be relevant and noise coming from input and architecture composition.īut, a difference of factor 2 to 5, or even higher, should be seen as actual meaningful difference of that platforms, where the lower is clearly less suited for the workload when efficiency is in one mind.įor raw performance the "Sum MiB/s" column can be used as, again rough, estimation.Įfficiency score is calculated by dividing the sum of all benchmark result (unit MiB/(s*core) by the W/Cores metric, due to Watt being J/s this means the score has the unit of MiB/Joule and thus makes only sense when observed over time. It produces an efficiency score, which should be seen as "order of magnitude" score, i.e. We use the PBS client benchmark as it replicates a real workload close to 1:1, and we use the compilation of the client as using a modern compiler is one of the hardest stress tests which is still replicating actual workload. Note that modern CPUs are really complex, benchmarks should always be seen as such. This article is using the benchmark included in the Proxmox Backup Server client and building said client from source as rough (!) comparison for different CPU performance and efficiency.
