Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 18479
  • 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

Cadence Virtuoso Memory Limitation Issue

jdp721

Hi,

After completing a transient simulation (that generates ~ 2-3GB of psf files) in Virtuoso ADE-L, when the data tends to load in the ViVa display window, a dialog pops up (please see attached scrrenshot) indicating some kind of dearth in memory.

This doesn't always occur, but at times - and if this dialog comes, the data doesn't load (ViVa window remains blank) or partially loads.

Can you please indicate which memory does this refer to, and any setting in Virtuoso that can be tweaked to resolve this?

Thanks.

Parents
  • Andrew Beckett

    You didn't say which version of Virtuoso you're using. It looks as if it's IC616 or before though, in which case the simplest solution is to run Virtuoso in 64-bit mode. This can be achieved either by:

    virtuoso -64

    or:

    setenv CDS_AUTO_64BIT ALL # (ALL may not be what you want, so check the documentation for this env var)
    virtuoso

    By default virtuoso runs in 32-bit mode in these versions which means your memory limits are about 4Gbytes (a bit less). In IC617 there is only 64-bit virtuoso available, so there's no need to do this. Historically we supported both 32-bit and 64-bit versions because a) sometimes people were running on 32-bit OS (although those haven't been supported for years, so that's no longer a reason) and b) there is a small performance penalty - it's pretty small - for running in 64-bit because of the increased memory access (any pointers double in size, so you consume more memory). However, those reasons weren't really worth the pain of running out of memory too often, so that's one of the contributing reasons why we only have 64-bit virtuoso from IC617 onwards.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    You didn't say which version of Virtuoso you're using. It looks as if it's IC616 or before though, in which case the simplest solution is to run Virtuoso in 64-bit mode. This can be achieved either by:

    virtuoso -64

    or:

    setenv CDS_AUTO_64BIT ALL # (ALL may not be what you want, so check the documentation for this env var)
    virtuoso

    By default virtuoso runs in 32-bit mode in these versions which means your memory limits are about 4Gbytes (a bit less). In IC617 there is only 64-bit virtuoso available, so there's no need to do this. Historically we supported both 32-bit and 64-bit versions because a) sometimes people were running on 32-bit OS (although those haven't been supported for years, so that's no longer a reason) and b) there is a small performance penalty - it's pretty small - for running in 64-bit because of the increased memory access (any pointers double in size, so you consume more memory). However, those reasons weren't really worth the pain of running out of memory too often, so that's one of the contributing reasons why we only have 64-bit virtuoso from IC617 onwards.

    Regards,

    Andrew.

Children
No Data

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.