editor's blog
Subscribe Now

An Almost-Cloudy San Diego Day

Not long ago we looked at how EDA is shaping up in the cloud, including work that Synopsys has been doing to make VCS available for bursty relief usage. I was fortunate enough to attend a demo session to show how what has heretofore been an interesting theoretical discussion could be made concrete.

Synopsys spent a lot of effort on cloud computing at DAC this year, including a cloud partners booth. Various names, both obvious and some not so, were in the booth: Amazon, NetAp, Cisco, CloudPassage, Univa, Platform Computing, Xuropa, and EVE. Most of these guys provide a variety of services to bolster the Infrastructure as a service (IaaS), Platform as a service (PaaS), or Software as a service (SaaS) layers of any EDA offering. They appear to have very specific EDA (not just Synopsys) messaging.

In the demo session itself, we saw a bit more of Synopsys’s VCS specifics. As mentioned before, their setup involves a master node and multiple work nodes. Each cloud-computing instance (CCI) node consists of an 8-core Nehalem machine with 23 GB of memory for the 8 cores, along with a single VCS license. You can then requisition clusters consisting of multiples of 8 nodes, sizing up to hundreds of nodes (although they want advance notice on really large requests for now so they can set that up with Amazon; they don’t currently have them lying around because that costs money and there’s not that much demand yet).

They showed the scripts used to get things set up. The bring-up process lasts about a half an hour (they didn’t try to run that live), which might sound like a long time until you realize that, in that time, you’ve gone from nothing to, potentially, a multi-hundred-server compute farm.

I’d like to report on how they then went into the cloud and ran an example OpenSPARC simulation. That was the plan. But the unthinkable happened. And I totally felt for the guy running the demo. I mean, it’s the nightmare scenario for any of you (and me) who have done demos: you go to where the files are all ready to be uploaded and run… and… they’re gone. Completely gone. Like, the folder isn’t even there.

Turns out that a hard drive died on the Synopsys campus. The drive housing the project they were going to demonstrate. File it under “W” for “WT…” well, you know how that one ends. Yeah, crazy. So there wasn’t time to reconstruct it on another drive and start again. So we’ll have to report later when we see things actually happening in the cloud.

Leave a Reply

featured blogs
Mar 26, 2019
Many industrial electronics OEM designers use the word “rugged” to describe their board-level interconnect needs. While rugged can mean different things to different people, it usually includes the ability to withstand high shock and vibration applications, mainta...
Mar 26, 2019
It's CDNLive! Well, not today, Tuesday and Wednesday, April 2nd and 3rd at the Santa Clara Convention Center. So I have eight things you can do to get the most out of CDNLive and go home with a... [[ Click on the title to access the full blog on the Cadence Community si...
Mar 25, 2019
Do you ever use the same constraint templates in multiple projects? Now, with PADS Professional VX.2.5, you can easily import and export constraints from one project to the next. Constraint templates enable application of complex rules to multiple nets. They help ensure a smo...
Jan 25, 2019
Let'€™s face it: We'€™re addicted to SRAM. It'€™s big, it'€™s power-hungry, but it'€™s fast. And no matter how much we complain about it, we still use it. Because we don'€™t have anything better in the mainstream yet. We'€™ve looked at attempts to improve conven...