Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Virtuoso Slow Down after Large Memory exhaustion

Status
Not open for further replies.

pancho_hideboo

Advanced Member level 5
Joined
Oct 21, 2006
Messages
2,847
Helped
767
Reputation
1,536
Reaction score
732
Trophy points
1,393
Location
Real Homeless
Activity points
17,490
I use very complex and very heavy post processing with ViVa in Cadence Virtuoso.
However I always encounter "Swap Activity Warning".

Once I encounter "Swap Activity Warning", Virtuoso is very slow down and never recover normal operation speed, even if I close ViVa.

I have to restart Virtuoso to recover normal operation speed.

I think it is because Virtuoso can not release allocated memory.

Is ther any method to recover normal operation speed without restarting Virtuoso ?
 

Attachments

  • 2017-1215-1406-52.png
    2017-1215-1406-52.png
    27.2 KB · Views: 234

Several Virtuoso submodules do not run garbage collection when exiting. Did you try OS garbage collectors like, e.g. (I don't know your OS)
garbage_collection.png ---> garbage_collection.png or clean_memory.png ?
 

Did you try OS garbage collectors like, e.g. (I don't know your OS)
IC6.1.7 on Linux.
I don't think there is garbage collection.

And there is enough affordable memory as far as I see it by "xosview".
 
Last edited:

I have no experience with that tool but wonder whether
there are VM settings associated with it that could help
(like, perhaps, setting a physical memory use limit that
is more in line with hardware reality). Or maybe there are
Linux swap setting which you could optimize for this use
rather than more general "play nice" rules that come
default.
 

I have no experience with that tool
Try to plot many many subwindows or windows in ViVa.

but wonder whether there are VM settings associated with it that could help (like, perhaps, setting a physical memory use limit that is more in line with hardware reality).

Or maybe there are Linux swap setting which you could optimize for this use rather than more general "play nice" rules that come default.
I think none of them are helpful.

(1) There is no problem for simulation which exhaust more memory.
(2) There is no problem for Wavescan in IC5.

I think problem is in ViVa.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top