
I need to identify memory used by caches etc.


fail to explain why all the physical RAM is used up. #> Vcells 982837 7.5 1922617571 14668.5 2001035795 15266.7Ĭreated on by the reprex package (v0.3. How do I find out (in Powershell) what process/whatever uses the most memory Edit: I am trying to figure out how to use Powershell to find out whats using all the physical memory in case Task Manager etc. 2.Locate and then click the following registry subkey: HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session. #> Ncells 511114 27.3 1145652 61.2 628574 33.6 To do this, follow these steps: 1.Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list or press Windows. #> used (Mb) gc trigger (Mb) max used (Mb) #> sysname release version nodename machine If I push it even further R/RStudio seems to start using the disk to store stuff, or just says no. It looks like I can use most of my physical memory without changing any settings or command line arguments. It's instructive to open the Windows Task Manager and watch the memory usage as you do this. I have 24Gb physical RAM, Windows 10 64 bit. Apparently you need to set a command line parameter but I can't find how to do this? 256MB or less (common on older Dells and such)), cannot hold enough to run the program that's complaining (left-click My Computer (or Computer in Vista) in Start Menu, right-click the HDD you want to check and click Properties in that menu to see how much room you have got, should be 300-500MB at least) best fix for this is to delete or copy any data/files you dont need, elsewhere to free up space (another drive/cds etc).R and RStudio memory usage documentation is surprisingly awful.

One thing it could possibly be, is your HDD is full to the point where the swap file (virtual memory, a space used on your hard drive to cache parts of running programs, especially if installed RAM memory is not a large amount i.e. We will need more details, any more info in the warning window when it pops up (like paths to the faulting program or file), what is your computer's specifications/operating system/brand/ram memory/hard disk drive capacity etc (as much as you can tell us, otherwise its like trying to find how long a piece of string is ).
