Stats

Locked Locked
Replies 4
Subscribers 124
Views 13648
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Slow save statements..

So I'm running cadence 6.1.3 and I'm trying to do an APS simulation. I found that if I do a saveOption('save "all"), it wouldn't save all. In fact it would randomly throw away nodes that should have been saved (i.e. nodes with two end points connected to transistors).

So, I switched to save selected.

I wrote a small script to generate the save script to save a bunch of nodes and pasted the result into my ocean script. This ended up being ~ 100+ signals in a save statement.

Now, when I try launching the simulation it takes MUCH longer to start as it's spending a long time parsing the save statements.

Is this what other people are seing? Does the save command really only work well with just a few nodes?

Andrew Beckett over 15 years ago

Mark,
I wouldn't expect this; it should not present any kind of noticeable slow down to have a large number of explictly saved nodes (unless the list is really huge, maybe).
Please can you file a service request with customer support so this can be investigated in more detail, and if something needs fixing, it can be fixed.
Regards,
Andrew.
Cancel
Vote Up 0 Vote Down

Cancel
markbeck over 15 years ago

I am not seeing this in 5.1.41, but only in 6.1.3.
Created SR: 41815744
Thanks.
Cancel
Vote Up 0 Vote Down

Cancel
archive over 15 years ago

Try using a single save statement. In Spectre syntax it's:
save *
Cancel
Vote Up 0 Vote Down

Cancel
markbeck over 15 years ago

I failed to try the most basic 'fix'... shutdown for the weekend, restart on Monday. The problem seems to have magically disappeared.
As for the "save *", I've found that it doesn't work for APS hence the reason for explicitly declaring each and every net.
Cancel
Vote Up 0 Vote Down

Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.