"The chief architect behind Intel's Xeon line of server CPUs is leaving Chipzilla for greener pastures. Senior fellow and Xeon Chief Ronak Singhal's nearly 30-year tenure at the x86 giant will come to an end later this month, according to a CRN report, which The Register has independently confirmed. The Carnegie Mellon alum holds degrees in electrical and computer engineering, along with at least 30 patents involving CPUs. Singhal joined Intel in 1997 after spending the previous summer as an intern at Cyrix."
"After a year in Intel's Rotation Engineers Program, he spent the remainder of his tenure helping to develop some of the chipmaker's most consequential and, at times, controversial processors. Most notably, Singhal oversaw the core development of Intel's 22nm Haswell and 14nm Broadwell processor architectures. His innovations aren't limited to the datacenter either, with his architectural contributions playing a significant role in the success of Intel's Core and Atom processor families as well."
"Despite Singhal's contributions, Intel's Xeon division has faced steep competition over the past few years, not just from rival AMD but from a growing number of Arm-based custom cloud CPUs. Despite some missteps, the long-delayed Sapphire Rapids launch, which allowed AMD to extend its core count lead, Singhal is arguably leaving the Xeon division in the most competitive position it's held in years."
Ronak Singhal will leave Intel later this month after nearly 30 years as a senior fellow and Xeon chief. He holds ECE degrees from Carnegie Mellon and about 30 CPU patents. Singhal joined Intel in 1997 after interning at Cyrix and spent a year in the Rotation Engineers Program before focusing on processor architecture. He led core development of Intel's 22nm Haswell and 14nm Broadwell microarchitectures and contributed to Core and Atom families. Intel's Xeon business faces rising competition from AMD and Arm-based cloud CPUs, with AMD and Arm taking significant server market share. Recent Granite Rapids Xeon launches closed some gaps but key challenges persist.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]