EDA Licenses & Compute Farms

Running FlexNet license servers (lmgrd, vendor daemons, lmstat, three-server redundancy), treating licenses as the scarce resource in LSF or Slurm, reporting utilization, and bursting EDA work to the cloud.

Overview

Why this topic

On a chip team, the most expensive thing in the data center is often not a server. It is the right to run the software. Commercial EDA tools (simulators, synthesis, place and route, signoff) are licensed per concurrent user or per job, and those licenses frequently cost more per year than the hosts they run on.

That changes how a compute farm is run. A farm can have a thousand idle cores and still be full, because every simulator license is checked out. The infrastructure engineer's job is to keep the license servers up, make the scheduler aware of licenses, report how they are used, and decide when more cores, more licenses, or the cloud is the right answer.

Interview questions

  • Design a highly available license service for 3,000 farm hosts. Triad or independent servers?
  • Jobs pend for hours while hundreds of cores sit idle. How do you find out whether licenses are the bottleneck?
  • How do you make LSF schedule by license availability?
  • Leadership asks whether to buy 100 more simulator licenses. How do you answer with data?
  • Design a hybrid farm that bursts EDA jobs to a public cloud. What are the hard parts?
  • Compare the cost of on-prem capacity, cloud burst and more licenses for a tape-out crunch.

Sign up free to read the full topic

More AI Infrastructure topics

Start free on Cariara · Coding problems · System design studio