Does your statement explicitly refer to AMD CPUs?
I still have to investigate whether this KB article also reflects the optimum for ROME CPUs.
@nmym The Lenovo Bios may be better designed for optimal performance. After tuning the system by hand, I also asked Lenovo for the Optimal Bios settings and got the following answer with good result:
"the current recommendation is to set the UEFI Operating Mode to "Maximum Performance".
Please check if the "EfficiencyModeEn" parameter is set to "Auto" and not to "Enabled".
There was a FW bug, which should be fixed by the end of September. (UEFI CFE105D for pre-GA HW, UEFI CFE106D for GA HW)"
Our test system is already running VMware again to add a few more tests. Afterwards we will send the system back to Lenovo next week.
However, we ordered 4 systems. So I can contribute more tests in the coming weeks. Then also with optimal RAM equipment (8x64GB @3200MHz) and new Shared Storage Storwize V5030E.
I have sized the storage as follows:
4x Hosts with 2x16GB HBAs each. Redundant FC-SAN. Storage with 8x16GB HBAs, distributed on both fabrics. Single-Initiator Zoning for each Server-HBA to both Storage Controlers.
According to sizing tools (Capacity Magic / Disk Magic), the storage system then reliably delivers 90TB and approx. 120,000 IOP/s at <0.4ms. This meets our requirements.
@nmym Currently I can not check it myself, because I do not have such spare hardware.
I also design our new SR655 pool with an AllFlash Storwize V5030E on a Fiber Channel SAN. I only need 90TB @ 90K IOPs. So this is not about the highest performance in the storage area. My oppinion is that it's more important to have thin provisioning on the storage side and SCSI unmap support on the hypervisor.
But that's my opinion and Oliver sees it quite differently. That's legitimate, too.
We only use local storage in very few projects.
This test was only about the validation of the CPUs.
Is there anything new from the Xen Devs to Rome? I can't see any limitations, bug or failure.
I am happy to do further tests. Write to me if you are interested in anything.
@nmym Which drives do you mean? The M2-SSDs are relatively slow and only for the OS. Our Storwize V5K (Gen1) is only connected with 8GB fiber channel and can only handle 1400MB/s and 25k IOPS. That's not fast anymore... I just didn't have anything else to test.
We had the system two weeks ago attached to an IBM flash system 900. That makes up to 1.2 million IOPs at low latency. Under VMWare it was very fast. I couldn't test XCP-NG there, because the Storage was already in production.
we have just successfully tested this CPU for 3 weeks and we still have a Lenovo test system in our data center:
The configuration is as follows:
Its a CTO-Configuration:
1x ThinkSystem SR655 24x2.5" chassis
1x ThinkSystem AMD EPYC 7402P 24C 180W 2.8GHz Processor
2x ThinkSystem 64GB TruDDR4 3200MHz (2Rx4 1.2V) RDIMM-A
1x ThinkSystem M.2 SATA/NVMe 2-Bay Enablement Kit
2x ThinkSystem M.2 128GB SATA 6Gbps Non-Hot Swap SSD
(This is the XCP-NG Boot-Disk)
1x ThinkSystem SR635/SR655 x8 PCIe Internal riser
1x ThinkSystem SR655 x16/x8/x8 PCIe Riser1
1x ThinkSystem SR655 x16/x8/x8 PCIe Riser2
1x ThinkSystem Mellanox ConnectX-4 Lx 10/25GbE SFP28 2-port OCP
(LACP-Trunk 2x 10GB zu IBM G8264 vLAG)
1x Emulex 16Gb Gen6 FC Dual-port HBA
(Attached to Storwize V5k shared Block-Storage)
2x ThinkSystem 1100W (230V/115V) Platinum
hot swap power supply
2x 2.8m, 13A/100-250V, C13 to C14 Jumper Cord
Load tests were problem-free for days. The system is impressively fast.
processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7402P 24-Core Processor stepping : 0 microcode : 0x830101c cpu MHz : 2794.751 cache size : 512 KB physical id : 0 siblings : 16 core id : 0 cpu cores : 16 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu de tsc msr pae mce cx8 apic mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes x save avx f16c rdrand hypervisor lahf_lm cmp_legacy abm sse4a misalignsse 3dnowpr efetch bpext ssbd ibpb vmmcall fsgsbase bmi1 avx2 bmi2 rdseed adx clflushopt clw b sha_ni xsaveopt xsavec xgetbv1 clzero arat rdpid bugs : fxsave_leak null_seg spectre_v1 spectre_v2 spec_store_bypass bogomips : 5589.60 TLB size : 3072 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: