Increase desktop heap windows 2003

Organization of this section 1 Determining the desktop heap settings 2 Changing the desktop heap setting. This is the default maximum value of the desktop heap for Windows Server 32bit.

The maximum value of the desktop heap depends on the OS. For this reason, you should not set the value higher than is necessary. Commands that acquire maintenance information, and that are executed after abnormal termination of a HiRDB server process, are also processes activated by HiRDB, and they use desktop heap. Stop the HiRDB service. This problem occurs because of the desktop heap limitation. When you close some windows, and then try to open other windows, these windows may open.

However, this method doesn't affect the desktop heap limitation. This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.

Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows. Click Start , type regedit in the Start Search box, and then select regedit. If you are prompted for an administrator password or for confirmation, type your password, or click Continue. In the Value data section of the Edit String dialog box, locate the SharedSection entry, and then increase the second value and the third value for this entry.

By default, the Windows registry entry contains the following data in an xbased version of Windows 7 Service Pack 1. Memory allocations are dynamic in later operating systems. The default value of this entry is 20 megabytes MB. This memory is allocated for applications to use GUI objects such as fonts, menus, and windows. The SessionPoolSize registry entry specifies the session paged pool in megabytes. The default value for the session paged pool is 16 MB.

If sufficient memory is available, Windows may also allocate 32 MB. This memory is used for video driver allocations. The best way to increase the memory allocated to both the SessionViewSize and SessionPoolView entries is to increase the value of memory allocated by 16 MB, and then see whether the services are available to run applications after you increase the value of memory allocated to the SessionViewSize and SessionPoolSize entries.

If not, increase the value of memory allocated by 16 MB and try again. If you allocate more memory to increase the desktop heap, you may reduce the memory that allocated by the Terminal server to other resources, such as nonpaged pool, paged pool, and system cache. This will affect the performance of the Terminal server.

Also, when more memory is allocated to the SessionViewSize and SessionPoolSize entries, the memory allocated to map the kernel virtual space will be reduced.