editor's blog
Subscribe Now

Algorithms or Methodologies?

You see it two to four times a year from each EDA player: “x% Productivity Gains with y Tool!” Cadence recently had such an announcement with their Incisive tool; Synopsys has just had a similar story with FineSim.

As I was talking with the Cadence folks about this, I wondered: How much of this productivity gain comes as a result of engine/algorithm improvements, and how much as a result of methodology changes? The answer is, of course, that it comes from both.

But there’s a difference in when the benefits accrue. Engine improvements are immediately visible when you run the tool. Methodology changes: not so much. And there are actually two aspects to methodology.

The first is that, of course, a new methodology requires training and getting used to. So the first project done using a new methodology will take longer; the next one should be better because everyone is used to the new way of doing things. This is a reasonably well-known effect.

But there may be an extra delayed benefit: some methodology changes require new infrastructure or have a conversion cost. If, for example, you replace some aspect of simulation with a new formal tool, you have to modify your testbench and create the new test procedure from scratch. There may be, for instance, numerous pieces of IP that need to be changed to add assertions. These are largely one-time investments, with incremental work required on follow-on projects.

In this example, it may be that, even with the conversion work, things go faster even on the first project. But productivity will be even better next time, when much of the infrastructure and changes are ready and waiting.

As to the engines, I was talking to the folks at Mentor yesterday, and wondered whether improvements to the tools themselves become asymptotic: does there come a point when you just can’t go any faster? Their answer was, “No,” since there’s always some bottleneck that didn’t used to be an issue until the other bigger bottlenecks got fixed. The stuff that got ignored keeps bubbling up in priority, the upshot being that there’s always something that can be improved to speed up the tools.

Leave a Reply

featured blogs
Sep 21, 2018
在这我们谈论的不是您的叠层设计跟其他人比怎么样,而是您设计的 PCB 层叠结构,是刚性板、柔性板、刚...
Sep 21, 2018
  FPGA luminary David Laws has just published a well-researched blog on the Computer History Museum'€™s Web site titled '€œWho invented the Microprocessor?'€ If you'€™re wildly waving your raised hand right now, going '€œOoo, Ooo, Ooo, Call on me!'€ to get ...
Sep 20, 2018
Last week, NVIDIA announced the release of the Jetson Xavier developer kit. The Jetson Xavier, which was developed in OrCAD, is designed to help developers prototype with robots, drones, and other......
Sep 18, 2018
Samtec performs several tests in-house as part of our qualification testing on a product series; including Low Level Contact Resistance (LLCR). It measures the amount of resistance in a position on a part. LLCR is used in combination with several other tests to track the over...