AMD Eypc 7402P ?
-
@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.
-
Before installing Xen, the first thing I change is the BIOS power profile settings. In my experience, it works pretty well with
PerformanceandOS Control. For production, my choice is the latter because it gives to Xen the core frequency scaling management (boost) and saves energy when there's a low demand after hours.@nmym said in AMD Eypc 7402P ?:
When I set this to ondemand, my network speed drops. It's somehow ironic as I have the demand for this speed, but the process does not demand, resulting in slower network transfer
For benchmark purposes, try reducing the dom0 #vcpus (4 is good value IMHO for the tests). Since it's a high core count processor, a 8+ dom0 cores is good for hosting 100+ VMs but it might distort benchmark results because the packet processing will be spread across all dom0 cores. With the CPU governor set to
ondemandthe more cores you have the less will be the need to boost. This behavior doesn't occur inperformancedue to the cores being at the base clock minimum frequency. -
Does your statement explicitly refer to AMD CPUs?
I still have to investigate whether this KB article also reflects the optimum for ROME CPUs.
-
No, my systems are Intel-based but might work also for AMD processors. The only caveat is whether AMD fixed the C-STATES/MWAIT bug causing spontaneous reboots on the 1st gen architecture. Since ROME is a new arch, maybe it's not affected. The only way to be sure is enabling C-STATES and keep an eye on it.
That Citrix KB is my go-to reference about Xen power management. Very good article.
-
@tuxen I never saw such "performance mode" only very basic CPU settings, like cstate.
When i had C-state to auto I had never any issues with reboots (only had it running for 2 days straight), before I disabled the C-state.
I found out having C-state to auto my processors never reached their max clock frequence.
I did however never test to change the scaling-governor to performance.
I did not need to change this to performance to get full clockspeed when C-state was disabled. I just had to load the CPU. -
We're running this puppy :
Model: AMD EPYC 7352 24-Core Processor
Speed: 2300 MHzIf any of you want me to run tests, I can try
-
One socket right?
