On Wed, Dec 16, 2015 at 11:57 PM, Mike Williams <[email protected]> wrote: > How about on Windows running a 32bit process on 64bit OS with 8GiB of RAM? > Max mem usable is 4GiB, the limit for the virtual address space. Windows can > report available virtual address for the process, what is left for the heap > after the process is started which will be less than this. No point > artificially limiting it to half of this is there? For a 64 bit process this > is not practical, so what value should be used? On recent Windows, physical > RAM less 250MiB for OS and its data should be more than adequate for > maxmemtot to avoid paging and not be limiting. This suggests pushing the > logic for default values down into mch_ functions so they can OS specific > rather than applying a rough heuristic to all of them. > > TTFN >
If 64-bit Windows behaved as does 64-bit Linux, then a 64-bit process on a 64-bit OS on an 8 GB machine would get &maxmem == &maxmemtot == about 4G. I know because that's what I have on Linux. For a 32-bit process on a 64-bit machine I'm not sure what the "right" answer would be. Probably 2G, as the help implies, and if you want more than that (up to the maximum memory addressable by 32-bit code), set it in your vimrc. Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
