![]() ![]() What the Windows engineers have done instead is provide a variety of techniques to either shuffle the kernel/user allocation ratio about or provide other APIs to allow larger memory regions to be allocated and different portions of that to be mapped into the process address space on demand [ Even today this address space limit of 4GB is still in effect for 32-bit processes. That meant 2GB was reserved for the system (or kernel space) and 2GB for the application (or user space). The initial design decision was to split the 4GB virtual address space that every 32-bit process would be limited to into two halves. When Windows NT was first being developed back in the early 1990s you were lucky to find hard disks with a capacity over 2GB, let alone that much physical RAM. This article will outline the various memory constraints that affect 32-bit processes on the Windows platform and the solutions that both Intel and Microsoft provide for overcoming them through hardware, OS configuration or API changes. This kind of service is often deployed on some Big Iron hardware with the sole aim of allowing it free rein of the host machine – its job being to serve clients, preferably as many as possible and in the shortest possible time. ![]() Given the chance, they will devour as much RAM as you can feed them, using it for caching to reduce costly I/O requests. Large scale enterprise services like SQL Server and Exchange Server can be memory hungry beasts. ![]() Chris Oldwood presents techniques to provide extra memory. Some applications require a vast amount of memory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |