RWiki 24½ BETA - Windowsi ressursside häälestamine

Windowsi ressursside häälestamine

TODO.

Siia tuleb põhjalik loetelu parameetritest ja ressursisüsteemidest, mis vajavad eraldi tuunimist ning ka, kuidas need teineteist mõjutavad.

Kui mulle selle teemaga pinda käia, siis panen info rutem üles. Sest pikas plaanis tahan ma seda teha, aga see nõuab mõnevõrra aega ja keskendumist. Selle ettevõtmiseks on hea, kui leidub motivaator :)

SessionPoolSize

@ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\

http://www.brianmadden.com/Forum/Topic/97733
http://support.citrix.com/article/ctx115637
http://support.citrix.com/article/CTX114497

three 17” full screens with a resolution of 1280x1024 can properly use a seamless window application environment on a single screen.

MaxLVBMem = (3840 x 1024 x 24)/8 = 11.79648 MB
SessionPoolSize* = 16 MB

*Note: Microsoft recommends raising this in increments of 16MB (but not past 64MB).

http://www.tomshardware.com/forum/224776-33-display-cards-other
This memory is used for video driver allocations.

http://216.239.59.104/search?q=cache:vgBvIuK34W4J:www.jsifaq.com/SUBQ/tip8000/rh8057.htm+SessionPoolSize&hl=en
By default, the desktop heap is 20 MB, 104 MB for 64-bit operating systems, which is allocated for GUI objects, such as fonts, menus, and windows. The session paged pool defaults to 16 MB, 32 MB if enough memory is available, and is used for video driver allocations. The 64-bit operating systems defaults the session paged pool to 64 MB.

NB! limits: SessionPoolSize + SessionViewSize <= 512

http://support.microsoft.com/default.aspx?scid=kb;en-us;330174 - says that increasing SystemPages decreases resources left for Paged Pool.

SessionViewSize

@ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\

seems like the SessionViewSize = SessionPoolSize + 44MB,
for every size of SessionPoolSize

BUT
according to
http://blogs.msdn.com/ntdebugging/archive/2007/07/05/desktop-heap-part-2.aspx
seems like SessionViewSize is the range that contains the Desktop
heap. You also try to decrease Non-interactive desktop heap size and
winlogon heap size and disconnect heap size

NB! limits: SessionPoolSize + SessionViewSize <= 512

SessionImageSize

@ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\

sessionimagesize is for loading video driver. You can try to make it
smaller. When video driver does not load, THEN make it bigger.

SystemPages and ATI card

@ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\

http://www.compatdb.org/support/topics/85846_question_about_systempages_in_nt_2k_xp.html
http://www.google.com/search?q=atitweak&rls=com.microsoft:et:IE-SearchBox&ie=UTF-8&oe=UTF-8&sourceid=ie7
- atitweak suggest setting SystemPages to 0xFFFFFFFF

more about SystemPages - should not be used in conjunction
with /userva
http://www.exchangenewsgroups.net/group/microsoft.public.exchange.misc/topic6455.aspx#scroll_top=964

NonPaged Pool

NonPagedPoolSize @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\

The actual size of the pool will be always at least 128MB. The formula for calculating actual size of the pool is:

actual nonpaged pool size = 128MB + NonPagedPoolSize

where NonPagedPoolSize is the corresponding field's value in the registry.

I havent found any documentation mentioning this formula.

Paged Pool

PagedPoolSize @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\

about Paged Pool see:
http://support.microsoft.com/kb/312362
http://support.microsoft.com/kb/304101
http://www.kbalertz.com/kbNamed_935649/935649.aspx

http://support.microsoft.com/kb/312362:
possible maximum paged pool memory on a computer can be 343MB

BUT!!!
*
http://www.tokeshi.com/index.php?option=com_content&task=view&id=4599
http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-understanding-pool-resources.aspx
http://technet2.microsoft.com/windowsserver/en/library/2de5c6af-f6a4-4ea0-8b78-df153663f6ed1033.mspx

-> on Win 2003
--> max paged pool: 650MB ! <-- (and for 64-bit it is nearly infinte)
max nonpaged pool: 256MB

but
http://technet2.microsoft.com/WindowsServer/en/Library/b1bda681-28b0-4339-a4ea-feb0fd9ff0c01033.mspx
says that max Paged Pool is
512 MB

see also:
http://blogs.technet.com/askperf/archive/2007/09/28/memory-management-x86-virtual-address-space.aspx

Subsystems\Windows (SharedSection)

* http://support.microsoft.com/default.aspx?scid=kb;EN-US;184802
* http://blogs.msdn.com/ntdebugging/archive/2007/07/05/desktop-heap-part-2.aspx
* http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx
* http://www.scheduler-usage.com/modules.php?name=Forums&file=viewtopic&t=1403 ja http://www.devnewsgroups.net/dotnetframework/t15947-max-limit-number-managed-windows-services-that-can-run-win-2000-server.aspx - huvitav jutt selle kohta, kuidas kolmanda ja neljanda parameetri seadmine mõjutab seda, kui palju service-id on võimalik käivitada
* http://www.rtems.com/ml/rtems-users/2004/september/msg00028.html - seondub samuti osaliselt eelneva teemaga
* http://support.microsoft.com/default.aspx?scid=kb;EN-US;184802 - huvitav lause: "The total desktop heap being used in the interactive and noninteractive window stations must fit into the 48-MB system-wide buffer."
*

note: the following is probably old note, you may ignore it

sharedsection seems to be contained in memory area specified by
SessionViewSize

additionally it looks like sharedsection does not help in increasing gdi
limits...
and in backup2 server (one of my machines) SessionPoolSize is less than resources already allocated by GDI (visible in poolmon)

so neither SessionViewSize or SessionPoolSize help here?
or is SessionViewSize simply ceiled by meeting PagedPoolSize in
this machine - ?
(in backup2 machine the SessionViewSize is so far been > than
resources used by GDI, as visible in poolmon)

Is it okay to reduce SessionImageSize ? It should somehow be
related to video driver memory.
Or should I increase it instead?

SystemCacheDirtyPageThreshold

http://support.microsoft.com/default.aspx?scid=kb;EN-US;920739

CAUSE
This problem occurs when you copy large files locally from a fast
disk to a slow disk. For example, this problem can occur when you
copy large files from a cluster disk to local system disk.
The System Internals Cache Manager uses a variable that is named
CcDirtyPageThreshold. By default, the value of
CcDirtyPageThreshold may be set too high for scenarios where
there are many lazy writes. By default, the CcDirtyPageThreshold
global kernel variable is set to a value that is half of the physical
memory. This variable triggers the cache manager's write throttles.
For example, if you are copying a file that is 1 GB, 500 MB of the file
is copied to the cache before the Cache Manager starts flushing the
dirty pages. Flushing 500 MB of dirty pages causes several page
faults. These page faults must be committed to the disk. When this
occurs, it can cause bottlenecks on slow disks.
Note A "dirty page" is a page that has been modified in the cache but
has not yet been written to disk.

"0x20" corresponds to a decimal value of 32 MB.
• The range of values for the
SystemCacheDirtyPageThreshold registry entry are as follows:
Minimum value: Total physical RAM in MB divided by 64
Maximum value: Total physical RAM in MB divided by 2
Default value: 0

The default value is a nonexistent key. If you add values that are out
of range, your computer will revert to the default behavior. The value
that you add is measured in MB.

MORE INFORMATION
To verify that you are experiencing this problem, use the !defwrites
command in the kernel debugger. This command displays the values
of the kernel variables that the cache manager uses, and it displays
the values of the threshold and of the actual dirty pages that are in
the cache. When you run this command, you may receive output that
resembles the following:
CcTotalDirtyPages: 14 (0 Kb)
CcDirtyPageThreshold: 130941 (0 Kb)
MmAvailablePages: 62445 (0 Kb)
MmThrottleTop: 450 (0 Kb)
MmThrottleBottom: 80 (0 Kb)
MmModifiedPageListHead.Total: 43 (0 Kb)
You may experience the problem that is described in this article if
the CcTotalDirtyPages value is close to the CcDirtyPageThreshold
value.

GDI handlite arv

* http://support.microsoft.com/default.aspx?scid=kb;EN-US;840342

Muu

* according to http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx seems like Desktop heap size is per process, and Session View is per session
*

Veelkord ülevaadata

* http://technet.microsoft.com/en-us/library/aa996184.aspx
* http://www.windowsitlibrary.com/Content/224/3.html

* http://support.microsoft.com/kb/102985

Küsimused:

could it be that SessionViewSize contains:
- Desktop Heap
- SessionImagesize
- GDI pools
?

Veel infoks

* Handle'te loomiseks kasutakse NonPaged Pool'i. Minu masin suutis 128MB NonPaged Pool-iga tekitada u 1 miljon handlit (see ei ole, et 128MB mahtab 1 miljon handlit, kuna see 128MB oli pooli kogmaht, koos draiveritega ja muu kraamiga, mis võttis vast vähemalt pool sellest, aga täpselt ei mäleta), peale seda läks masin rivist välja. Üldiselt ei tasu ületada seda handlite tekitamise piiri niimoodi, sest võivad tekkida isegi NTFS vead. Mõned installerid tekitavad suure handle'ite lekke, seega tasub vaadata, et NonPaged Pool oleks piisava suurusega.

* NOD32 antiviirus kräshib arvuti, kui ta failisüsteemi kaitse on sisse lülitatud ja NonPaged Pool täis saab.

* Remote Desktop ei kasuta GDI poole ja seega suudab mõningaid GDI mahukaid programme suuremas koguses avada, ilma et graafika tõrkuma hakkaks.

Utiliidid erinevate ressursside jälgimiseks

* poolmon.exe - näitab ära muuhulgas GDI Paged pool'ide hetkesuurused (TODO: selle jälgimine) ja Registry Paged pool'ide suurused (NB! näiteks otsing üle terve registry või registry export võib tekitada mõneks ajaks paged pool'i või mitu pool'i, mille suurus on üle saja MB; kui see protsess panna suspendi peale või lõpetab töö ära, siis nende pool'ide suurus tasapisi väheneb. Juhul kui juhtub, et selle asja käigus paged pool'ide summaarne suurus läheb nii suureks, et süsteemi Paged Pool tühjaks saab, ei suuda Windows peale seda enam registry'sse muudatusi salvestada, isegi kuigi pärast registry pool'id kokku tõmbuvad. Samuti olen täheldanud, et mõnikord on kohe peale bootimist registry pool'id maksimaalse suurusega ja jäävadki selliseks, raisates süsteemi Paged Pool mälu)

* Perfmon - näitab ära Free System Page Table Entries (seondub SystemPages atribuudiga registris), PagedPool ja NonPagedPool kasutuse

* Task Manager - näitab hetke PagedPool ja NonPagedPool kasutust

* dheapmon.exe - näitab ära Desktop Heap-ide limiidid ja kasutatuse (installi juhendi leiad siit: http://blogs.msdn.com/alejacma/archive/2008/07/29/how-to-use-dheapmon-exe-to-troubleshoot-desktop-heap-issues.aspx)

* Process Explorer - näitab ära PagedPool ja NonPagedPool limiidid, kui Debug Symbols on installitud

* Performance Logs and Alerts - Windows'i service, mis võimaldab häälestada hoiatusi ja evente, mis käivituvad, kui mingi ressursi kasutus või vaba maht ületab või on alla mingi ettenähtud normi. Samuti võimadab nende näitajate logimist failidesse.

* TODO

Minu enda häälestuse reg faili sisu:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"ClearPageFileAtShutdown"=dword:00000000

"DisablePagingExecutive"=dword:00000001

"LargeSystemCache"=dword:00000000

"SecondLevelDataCache"=dword:00000400

"PhysicalAddressExtension"=dword:00000001

"SessionImageSize"=dword:00000020

"LargePageMinimum"=dword:ffffffff

"EnforceWriteProtection"=dword:00000000

"PoolUsageMaximum"=dword:00000001

"PagedPoolQuota"=dword:00000000

"NonPagedPoolQuota"=dword:00000000

"SystemCacheDirtyPageThreshold"=dword:00000100

"PoolTagOverruns"=dword:00000001

"PagedPoolSize"=dword:ffffffff

"NonPagedPoolSize"=dword:04100000

"SystemPages"=dword:ffffffff

"UnusedFileCache"=dword:00000001

"DisablePagedPoolHint"=dword:00000001

"IOPageLockLimit"=dword:10000000

"SessionViewSize"=dword:0000006c

"SessionPoolSize"=dword:00000040

"WriteWatch"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters]

"AppLaunchMaxNumPages"=dword:00000fa0

"AppLaunchMaxNumSections"=dword:000000aa

"AppLaunchTimerPeriod"=hex:80,69,67,ff,ff,ff,ff,ff

"BootMaxNumPages"=dword:0001f400

"BootMaxNumSections"=dword:00000ff0

"BootTimerPeriod"=hex:00,f2,d8,f8,ff,ff,ff,ff

"MaxNumActiveTraces"=dword:00000008

"MaxNumSavedTraces"=dword:00000008

"RootDirPath"="Prefetch"

"HostingAppList"="DLLHOST.EXE,MMC.EXE,RUNDLL32.EXE"

"EnablePrefetcher"=dword:00000003

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems]

"Required"=hex(7):44,00,65,00,62,00,75,00,67,00,00,00,57,00,69,00,6e,00,64,00,\

6f,00,77,00,73,00,00,00,00,00

"Windows"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\

74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,63,\ 00,73,00,72,00,73,00,73,00,2e,00,65,00,78,00,65,00,20,00,4f,00,62,00,6a,00,\

65,00,63,00,74,00,44,00,69,00,72,00,65,00,63,00,74,00,6f,00,72,00,79,00,3d,\

00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,68,00,61,00,\

72,00,65,00,64,00,53,00,65,00,63,00,74,00,69,00,6f,00,6e,00,3d,00,38,00,31,\

00,39,00,32,00,2c,00,36,00,35,00,35,00,33,00,36,00,2c,00,32,00,35,00,36,00,\

20,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,3d,00,4f,00,6e,00,20,00,53,\

00,75,00,62,00,53,00,79,00,73,00,74,00,65,00,6d,00,54,00,79,00,70,00,65,00,\

3d,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,\

00,65,00,72,00,44,00,6c,00,6c,00,3d,00,62,00,61,00,73,00,65,00,73,00,72,00,\

76,00,2c,00,31,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,44,00,6c,00,6c,\

00,3d,00,77,00,69,00,6e,00,73,00,72,00,76,00,3a,00,55,00,73,00,65,00,72,00,\

53,00,65,00,72,00,76,00,65,00,72,00,44,00,6c,00,6c,00,49,00,6e,00,69,00,74,\

00,69,00,61,00,6c,00,69,00,7a,00,61,00,74,00,69,00,6f,00,6e,00,2c,00,33,00,\

20,00,53,00,65,00,72,00,76,00,65,00,72,00,44,00,6c,00,6c,00,3d,00,77,00,69,\

00,6e,00,73,00,72,00,76,00,3a,00,43,00,6f,00,6e,00,53,00,65,00,72,00,76,00,\

65,00,72,00,44,00,6c,00,6c,00,49,00,6e,00,69,00,74,00,69,00,61,00,6c,00,69,\

00,7a,00,61,00,74,00,69,00,6f,00,6e,00,2c,00,32,00,20,00,50,00,72,00,6f,00,\

66,00,69,00,6c,00,65,00,43,00,6f,00,6e,00,74,00,72,00,6f,00,6c,00,3d,00,4f,\

00,66,00,66,00,20,00,4d,00,61,00,78,00,52,00,65,00,71,00,75,00,65,00,73,00,\

74,00,54,00,68,00,72,00,65,00,61,00,64,00,73,00,3d,00,33,00,32,00,00,00

; "Windows"="%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=8192,65536,256 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=32"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]

"DeviceNotSelectedTimeout"="15"

"GDIProcessHandleQuota"=dword:00003a98

"TransmissionRetryTimeout"="90"

"USERProcessHandleQuota"=dword:00003a98

"LoadAppInit_DLLs"=dword:00000001

"USERPostMessageLimit"=dword:00003a98

"__DesktopHeapLogging"=dword:00000001

Muud häälestused

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

NoLowDiskSpaceChecks = 1 - lülitab välja kettaruumi hoiatused

Kui RDP clipboard ei tööta

http://www.remkoweijnen.nl/blog/2007/10/25/rdp-clipboard-fix/
Lisaks on lehel http://blogs.msdn.com/rds/archive/2006/11/16/why-does-my-shared-clipboard-not-work-part-1.aspx
selline kommentaar:

As for the old version with this problem, there is a software workaround for developers... a) record the clipboard sequence number in your WM_DRAWCLIPBOARD handler, b) create a timer in which you call GetClipboardSequenceNumber() and compare to the last number you received in WM_DRAWCLIPBOARD. If those numbers differ, you know you've been dropped from the notification chain (or perhaps some dipshit app has been inserted in front of you and isn't passing along messages), and should re-add yourself. In this way, you can avoid user intervention such as having them restart the application.

Veateade "Cannot load UDM IPX/SPX SUPPORT" DOS programmide käivitamisel

http://www.computing.net/answers/windows-xp/cannot-load-udm-ipxspx-support/65876.html

Group Policy Editor for Windows XP Home

http://bogdan.org.ua/2007/11/15/windows-xp-he-home-edition-gpedit-msc-group-policy-editing-via-registry.html

Võib juhtuda, et tahad lisaks kopeerida oma masinasse ka faili wsecedit.dll, mida ülal viidatud paketis pole, siis küsi sõbralt. Selle faili installimiseks tuleb samuti anda käsk regsvr32 wsecedit.dll

Lisaks on soovitatud seda programmi: http://www.dougknox.com/xp/utils/xp_securityconsole.htm

Enabling administrative shares for Windows XP Home

http://www.oakdome.com/lab/?page_id=141

Variant ka:

http://answers.yahoo.com/question/index?qid=20080529195513AAe2X6D

Veebipõhine RDP

http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx

Recovery Console AllowAllPaths etc

http://commandwindows.com/recovery.htm

[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole]

SetCommand = 1

Alt-Tab CoolSwitch dimensions