DancinJack wrote:Yeah, those Revit models probably own RAM. I think the program requires 4GB just to run.
wibeasley wrote:How much virtual memory was it using?
flip-mode wrote:wibeasley wrote:How much virtual memory was it using?
I have no idea.
flip-mode wrote:It's set to be managed by Windows - no custom setting. Currently it reads as 8061 mb. You suggest I manually set it to 12000 mb?
The amount of consumed memory isn't the issue (from my perspective). It's why it crashed if the virtual memory still had room.Krogoth wrote:It isn't that difficult to use GBs of memory when you are using professional-level applications.
PrincipalSkinner wrote:I'm doing Java development and have switched from 32 bit Win 7 to 64 bit Ubuntu. Suddenly, 4GB seems tight. Thinking of getting 12GB or even 16GB for new build. Linux kernel has built it support for ramdisk.
thegleek wrote:Yeah, another 8gb user here... I could use +8gb myself! My system is constantly using 6.1gb of physical ram.
morphine wrote:thegleek wrote:Yeah, another 8gb user here... I could use +8gb myself! My system is constantly using 6.1gb of physical ram.
See how much that is used for caching. Chances are, the actual memory used is far lower, and the rest is filesystem cache, which is a good thing (tm). Unless you hear/feel your machine hitting the HDD all the time, you have RAM to spare.
morphine wrote:Task Manager (Ctrl+Shift+Esc), Performance tab.
thegleek wrote:morphine wrote:Task Manager (Ctrl+Shift+Esc), Performance tab.
Task Manager is so 90's... Haven't used that in decades... Move on to the Process Explorer and be FREE! (and tell me where to look in there once u get rid of task manager!)
The Standby list contains unmodified pages that have been removed from process working sets, which effectively makes the Standby list a cache. If a process needs a page that is on the Standby list, the memory manager immediately returns the page to its working set.
All pages on the Standby list are available for memory allocation requests. If a process requests memory, the memory manager can take a page from the Standby list, initialize it, and allocate it to the calling process. This is called repurposing a page.
Pages on the Standby list are often from recently used files. By keeping these pages on the Standby list, the memory manager reduces the need to read information from the disk. Disk reads can decrease system responsiveness.
To determine how much memory a particular user scenario requires, we recommend that you monitor the number and priority of the pages on the Standby list.
Windows 7 SuperFetch™ works with the memory manager to set priorities for pages on the Standby list. Pages that have recently been placed on the Standby list start with a high priority, which slowly decreases over time. If the system has too little memory to handle the workload, only a small percentage of the pages on the Standby list have a low priority. By monitoring the number of pages at different priorities, you can determine whether the system would benefit from increasing the amount of installed RAM.
Overall, the goal is to ensure that the system can maintain recently referenced pages in memory and still have enough available memory to satisfy any immediate memory needs.
Users browsing this forum: Google [Bot] and 1 guest