In part 1 of this series we looked at where Revit stores the version (build) number of the Revit product within a journal file. In part 2, we looked at where Hardware information is stored in a journal file.
In this part of this series we will look at where Revit Products capture Memory usage information during a session of Revit.
This information is scattered throughout the file in different places. It is captured at different times within the application.
VM Delta tells you the amount of memory that is available since the last time the item was recorded in the journal file. Basically, it lets you know how you are doing in relation to memory usage within Revit. The System (Kb) section tells you how much memory is available out of the total available system memory (that is available to Revit). The numbers are in KB so they are a little hard to read, but you don't want to see your available memory dip below 100 MB, this is where you will start to see problems.
The way product support uses this information is to find any error messages (we will talk about that in the next part) and then to see how Revit is doing with memory usage. We use this information to help to understand if Revit starting to run out of memory while trying to performance a task.
Next time, error messages in a journal file.