Synopsys Webinar | Available On-Demand
Bursting EDA workloads from on-prem to cloud is a challenge for most on-prem environments that are increasingly running out of capacity due to the growing complexity of advanced-node designs. For massively parallelized workloads, such as library characterization, implementation and physical verification, engineers currently need to split their designs between on-prem and cloud execution if they want to leverage the scalable compute capacity on cloud. Depending on the design, this is a tedious activity that eats away at precious engineering productivity. And once job execution is complete, the process to transfer output data back from cloud to on-prem and aggregate it with output generated on-prem adds to this overhead. In this session, we will discuss a unique approach to enabling a true hybrid cloud environment architected specifically for EDA workloads which enables engineers to submit a large job exclusively on-prem automatically splitting the job, routing selective worker traffic through a secure network for cloud execution, and syncing data generated on cloud back to on-prem storage for further processing in the flow. Along with license management automation, hybrid cloud optimization can radically improve engineering productivity and enhance the coverall cloud experience for SoC design.
Head of Cloud Product Management
Synopsys
Vikram Bhatia is head of cloud product management at Synopsys. He's responsible for building the industry's first completely browser-based EDA-as-a-Service platform, Synopsys Cloud. He has over 25 years of experience in product and GTM strategy, and prior to joining Synopsys, he served in a variety of leadership roles at organizations such as Microsoft, NetApp, Oracle, and HP, focusing on various cloud transformation initiatives. Vikram has a Bachelor of Technology degree from the Indian Institute of Technology Kanpur, and graduate degrees from the Colorado School of Mines and the Indian School of Business.
Short description goes here. Character count is limited by the card size, which is currently set to XS. Card size is adjustable via the Card Container component.