-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime #245
Comments
What step is running for so long? This is the largest memory block that I've generated. Likely, I suspect it is timing characterization. This can be sped up a bit if you have parallel simulation tools, but it's ultimately a bottleneck that needs to be addressed. The alternative now is to rely on the regression models, but these are not calibrated. We would welcome contributions to help with this |
Yes, Xyce would be a parallel simulator, but it needs to be compiled as such. This is stuck running extraction. Which version of magic are you using? There is likely an issue with that. |
My magic is version 8.3.363 What should be the correct version to use? |
That is correct: Line 10 in 0937f86
What kind of machine? How much memory is it using? |
Im using linux server, about 1.75T memory |
It's using 1.75TB?? That is the problem, it is paging to swap. This sounds suspicious though. How much physical memory is in the machine? |
It could be a memory leak in magic. |
Hi I am trying to run a 16kbyte SRAM on sky130. Is it normal that it will take couple of weeks to generate?
Mine has been running for 1 month now. It generate a temp.gds and I don't see any errors flag but its still finishing.
So Im curious to know is couple of weeks a normal runtime for ex. 16kbyte memory ?
The text was updated successfully, but these errors were encountered: