Wa_emtsubject: "emtsubject:itinformationtechnology/visualcomputing/rendering,emtsubject:itinformationtechnology/cloudcomputing,emtsubject:itinformationtechnology/analytics,emtsubject:itinformationtechnology/codemodernization,emtsubject:itinformationtechnology/softwaredevelopment,emtsubject:itinformationtechnology/computervision,emtsubject:itinformationtechnology/visualcomputing/videogamedevelopment,emtsubject:itinformationtechnology/storageandmemory,emtsubject:itinformationtechnology/platformanalysistuningandperformancemonitoring,emtsubject:itinformationtechnology/hpchighperformancecomputing,emtsubject:itinformationtechnology/aiartificialintelligence,emtsubject:itinformationtechnology/visualcomputing/mediaprocessing,emtsubject:itinformationtechnology/bigdata,emtsubject:itinformationtechnology/enterprisecomputing,emtsubject:itinformationtechnology/visualcomputing,emtsubject:itinformationtechnology/iotinternetofthings,emtsubject:itinformationtechnology/networking", Wa_curated: "curated:donotuseinexternalfilters/hidefromuam", Wa_rsoftware: "rsoftware:inteloneapitoolkits,rsoftware:developmenttools", Wa_emttechnology: "emttechnology:inteltechnologies/intelsecuritytechnologies,emttechnology:inteltechnologies/oneapi,emttechnology:inteltechnologies/intelgraphicsandvisualtechnologies",
#CENTOS AMD LINPACK BENCHMARK UPDATE#
building binutils 2.30 + GCC 8.0.1 profile guided optimization based RPMs for CentOS 7 were ~38% faster on newer KernelĬore CPU Avg_MHz Busy% Bzy_MHz TSC_MHz IR100.00 2563 1996 5090and 1 cpu thread load hits the max 3.0Ghz turbo speedģ0 47 3 0.11 2970 1996 17So looks like it's something to do with either my 4.15 Kernel update or additional tweaks I did manually.Ĭore CPU Avg_MHz Busy% Bzy_MHz TSC_MHz IRQ C1 C2 C1% C2% But haven't seem anyone mention this yet and whether it's unique to AMD EPYC + CentOS combo on ELrepo mainline 4.15 kernels ?Īlso seems there were definite performance improvements switching from CentOS 7.4 3.10 Kernels to 4.15 mainline Kernels i.e. Kernel:watchdog: BUG: soft lockup - CPU#8 stuck for 22s! seems raising the kernel.watchdog_thresh value from 10 seconds to 20 seconds fixed it though. Kernel:watchdog: BUG: soft lockup - CPU#8 stuck for 22s! Kernel:watchdog: BUG: soft lockup - CPU#21 stuck for 22s! Kernel:watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 48 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10Ĥ8 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10Ĥ8 x System Call Overhead 1 2 3 4 5 6 7 8 9 10Ĥ8 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10Ĥ8 x Pipe-based Context Switching 1 2 3 4 5
0 kommentar(er)
