![]() This is all good info, but ultimately not a good reason to leave what is clearly a bug in place. Incidentally, MacOSX is originally based on the Mach kernel, which is a derivative of BSD Unix from which FreeBSD descends. I actually use Windows 10 and not MacOSX - my understanding is that Windows VM tends not to swap until physical RAM is exhausted, but I'll need to check this to be certain. 64 bit processes can address a lot more than 4GB of RAM - a 4GB address space is the limit for a 32 bit process. On Linux, this can even be configured through `/proc/sys/vm/swappiness`. I imagine given it's origins that this is something that MacOSX could do too. ![]() With sufficient RAM available, most operating systems will not swap to disk much. accessed frequently) then it won't be swapped to virtual memory. While it is relatively rare for a process to use a large amount of resident RAM, it certainly can happen and graphics programs are likely to be one of those that would use a lot of RAM. Quote: Even for computers that have 4 or more gigabytes of RAM available, the system rarely dedicates this much RAM to a single process. To give processes access to their entire 4 gigabyte or 18 exabyte address space, OS X uses the hard disk to hold data that is not currently in use. ![]() Let me point to some VM documentation on Apple's web site: I'm familiar with FreeBSD's VM system, and I know that macOS is different (actually quite different). That is not correct as far as the way macOS handles virtual memory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |