On the bottom right hand side of the Phoenix application one can see the memory usage. Sometimes it changes color. The color coding on memory size is just for advisement, indicating reaching limits on a 32 bit system. 32 bit systems has a limit around 2GB per process (Phoenix is one process): Yellow: 1GB<1.5GB – getting close to critical for 32bit systems Orange: > 1.5GB – critical on 32bit systems, as limit is ~2GB for a process This limitations are not an issue for 64-bit systems and those color warnings can be ignored.
I find saving a project can reduce the current memory usage; are they any other tips/workarounds for 32-bit systems to reduce the memory usage? Simon
Another issue I noticed with the color code - lets say you reach the orange zone when working on a project. Now, if you close the project (not Phoenix), the program still shows the same color code indicating that the memory usage remains as such even though a project is closed. Is that how it is or is it unintentional?
A guess for what you are seeing could be the operating system unloading unused memory at its discretion, so Phoenix could still be “allocated” memory it is no longer using, and it will be released when the operating system decides it is a good time to do so (such as loading another project). If this is the case, unfortunately there is not much we can do about that. If you see this often and have a project that you could share with us to investigate further, please send it to Support@pharsight.com. Many thanks, Ana
The only other tip we can offer for these situations with 32-bit is to restart Phoenix often. This would force cleanup of any memory loss. Ana