{"id":36716,"date":"2003-04-01T19:06:23","date_gmt":"2003-04-01T19:06:23","guid":{"rendered":"https:\/\/silvaco.com\/%e6%9c%aa%e5%88%86%e7%b1%bb\/smartspice-tips-memory-usage-modif-alter-non-convergence\/"},"modified":"2021-10-13T10:43:14","modified_gmt":"2021-10-13T17:43:14","slug":"smartspice-tips-memory-usage-modif-alter-non-convergence","status":"publish","type":"post","link":"https:\/\/silvaco.com\/zh-hans\/simulation-standard-zh-hans\/smartspice-tips-memory-usage-modif-alter-non-convergence\/","title":{"rendered":"SmartSpice Tips: Memory Usage, .MODIF & .ALTER, Non-convergence"},"content":{"rendered":"
\n

SmartSpice Tips: Memory Usage, .MODIF & .ALTER, Non-convergence<\/h1>\n

Introduction<\/h3>\n

When you run a long simulation time analysis the evaluated time points are normally all held in memory until the end time is reached. All the data is then written out to the output rawfile. This means a large amount of system memory can be used up and also has to be tracked. If in the input deck the line \u201c.OPTIONS RAWPTS=300 POST\u201d is included then as soon as the maximum number of points is reached given by \u201cRAWPTS=300\u201d then all the vector data is saved to the raw data output file and the memory is free to be re-used. In this way the output rawfile is incrementally increased in size every time this limit is reached. The memory required by the simulation run is therefore reduced, and with less memory to manage, the simulation is run faster. This is particularly useful on the PC platform where some of the memory is required for the operating system and RAM size is less than 1Gig.<\/p>\n<\/div><\/section><\/div>

<\/div>