When running timeextract on a large simulation run, my machine comes to a screeching halt. What is going on?
If your simulation has many (100s+) timesteps and many (10s+) patches, then when the XML parser (xerces) opens all those files to get information about the simulation, it uses up quite a bit of memory. If all the memory in your machine is in use, it will start swapping and will slow down to a crawl. To fix this, we have added a flag to the timeextract program. You can use -noxml (or –xml-cache-off). This will turn off the caching of the XML files. The downside of using this option is that timeextract may be slower. This new ability is made possible by the new API function (turnOffXMLCaching()) added to DataArchive?.h. This function can be used by other programs that use the DataArchive? if they so desire.
Related Questions
- When running a simulation from Project Navigator, the default simulation time is 1000 ns. How can I make the simulation run longer and/or change the default run time?
- I have a machine running X on Resnet. Why can I run applications on DICE machines and have them display on it?
- When running timeextract on a large simulation run, my machine comes to a screeching halt. What is going on?
