I have no idea what you're talking about. I can't find any record of the "viva" command having a "-maxthreads" option (I can't see it in the source either), and I don't know what this "cadence internal support" is you're referring to.

You didn't mention which version you're using or anything useful, to be honest.

Please contact customer support - this is highly likely to be data dependent and would be very hard to debug in a public forum.

Andrew

Hi, AB:

Thank you for your reply. Here is the link I am refer to, https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000007MpKpUAK&pageName=ArticleContent

I really want to follow your suggestions to use customer support. But after a few times, the results are very painful. I didn't get anything resolved but wasted a lot of time scheduling meetings with cadence support in the morning. 

most of the knowledge I get from cadence is from this forum, but not through the customer support. I know a lot of people have asked the questions before. There is no value to repeat the questions again and again.

my cadence version is 6.1.8-64b.500.23

I managed to make a typo in my original search which is why I didn't find that. I rather doubt it's relevant (note you could run "virtuoso -maxthreads 1"), but I very much doubt that this is the root of your problem - it's a very specific situation where the memory grows as redraw is done because multiple threads are used, but it should reduce again afterwards as the work drops off (the article doesn't make it clear). It's probably more likely to be due to memory not being reused quickly enough which will be some function of what exactly you're doing - and we're not going to get that here (no matter what you think of my other colleagues in support - note that I too am part of customer support).

I certainly won't be able to provide any assistance here as I'm on vacation for the next 10 days. Which was another reason why I was steering you to support.

Andrew

I managed to make a typo in my original search which is why I didn't find that. I rather doubt it's relevant (note you could run "virtuoso -maxthreads 1"), but I very much doubt that this is the root of your problem - it's a very specific situation where the memory grows as redraw is done because multiple threads are used, but it should reduce again afterwards as the work drops off (the article doesn't make it clear). It's probably more likely to be due to memory not being reused quickly enough which will be some function of what exactly you're doing - and we're not going to get that here (no matter what you think of my other colleagues in support - note that I too am part of customer support).

I certainly won't be able to provide any assistance here as I'm on vacation for the next 10 days. Which was another reason why I was steering you to support.

Andrew