Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I am a bit confused with all of the high performance simulation options in ADE-XL/GXL.
I am using IC 18.104.22.1686 with MMSIM 10.11.200
On ADE I have:
1. "Options->Job Setup->Max Jobs"
2. "Options->Run Options-> Run In"
3. "High-Performance Simulation->Mode, Multithreading options, Affinity"
4. "Options->Analog->Multithreading Options"
What is the up to date way to run my simulations as fast as possible?
The main reason I'm asking is that I've had some problems when setting things such as APS + Max Jobs=8. For example, I've had these settings and sent a small simulation with a few corners and after waiting 10 minutes it still hadn't started. In general, it seems to take minutes until simulations start running sometimes (and then they run very fast).
Can anyone help me on this?
In reply to tkhan:
I can run in either local or distributed, and I have plenty of licenses, as I am a student in an academic institute and we get an enlarged package, so I don't mind using a lot of licenses.
In reply to aditeman:
This controls the number of parallel simulations that may be run at once in ADE XL. If you are using multiple tests in ADE XL, or corners, or sweeping variables or parameters, each one of these counts as a "job", and they can be run in parallel (on the local machine, on a remote machine, or distributed using a queueing system). Also if using Monte Carlo, it can break up the number of monte carlo points into chunks, based on the number of available parallel runs.
2. "Options->Run Options-> Run In"
This is not that useful - it's more to do if you hit the "Run" button again before existing jobs have finished - maybe having changed some setup.
This allows an individual simulation job to take advantage of multi-core technology and do things like the matrix solve in parallel - so it can speed up an individual simulation. Processor Affinity should be left alone (it allows you to get absolutely the best performance by telling the simulator which CPUs in a multi-core machine are to be used, but this is only ever useful if you have complete control over the machine you're running on, and has to be set carefully and is not normally worth the bother of setting)
This is pretty much obsolete nowadays - it was an earlier form of (limited) multithreadhing. It controls the same thing that's on the High Performance Options setting now - but that's the preferred location (the high performance options) to set multi-threadhing.
In reply to Andrew Beckett:
Do you have any idea what could be causing a long delay to initiate simulations? In other words, I press the "run" button, and once in a while I can wait a minute or longer (sometimes I stop it out of frusteration) before the simulations actually start. I have, for example, waited over 10 minutes for a simple simulation to start, then changed servers, and had the whole simulation from start to finish take 20 seconds. Our system administrator has tried to look into it, but as it happens quite sporadically, we have no clue what could be causing it. I do have a feeling, though, that it mainly happens when I try to run on multiple CPUs...
Hi Andrew and others,
I am running a long sim for a delta-sigma converter. Is there an optimum number of threads to use? I have six processors available, but I seem to remember that someone saying that at some point the speed increase is minimal if you add more processors -- I just don't remember what that point of diminishing returns was.
In reply to Rob Gregoire:
It's quite hard to be precise about this - APS supports up to 32 cores these days - and I have customers using that number (for very large circuits - e.g. several million transistors and even larger numbers of parasitics), so your mileage may vary. Generally speaking it's bigger circuits that will benefit from more threads. Doing some quick experiments with different number of threads would allow you to assess this for your size of design. You can check the utilization figures too that are reported in the log file (bearing in mind that you really wouldn't expect it to be able to fully utiliize all threads anyway).
Andrew, thanks for the answer. As always, I'm am very appreciative of the time you spend here helping.