The information in this article applies to:
SUMMARYWhile increasing your working set size and locking pages in physical memory can reduce paging for your application, it can adversely affect the system performance. When making decisions for your application, it is important to consider the whole system, and then test your application under a heavily loaded system, such as the users of your application might have. MORE INFORMATION
The Win32 SDK provides a tool called the working set tuner (WST.EXE). The
working set tuner decreases the working set size, which decreases memory
demand. However, you can also choose to set the process working set minimum
and maximum using SetProcessWorkingSetSize() and/or lock pages into memory
with VirtualLock(). These APIs should be used with care. Suppose you have a
16-megabyte system and you set your minimum to four megabytes. In effect,
this takes away four megabytes from the system. Other applications may be
unable to get their minimum working set. You or other applications may be
unable to create processes or threads or perform other operations that
require non-paged pool. This can have an extremely negative impact on the
overall system. Additional query words: 3.50
Keywords : kbAPI kbKernBase kbMemory kbWinOS2000 kbDSupport kbGrpDSTools kbGrpKernBase |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |