Dwa triki na przyśpieszenie Windows 2000 i XP

Iceman_87th [ Generaďż˝ ]

ad 1. byc moze
ad2. to raczej nie chodzi o L2 cache :)

ntroot [ Chor��y ]

Tip #1: Set the 2nd Level Data Cache in the Registry
Microsoft says that NT/2000 will attempt to detect the amount of L2 cache on the processors from the HAL. If the system is not able to detect the processor cache it will set the following registry entry to a value of 0. This value tells NT and 2000 that the processors in your server have 256K of L2 cache.
HKEY_LOCAL_MACHINE\System\Current Control Set\Control\Session Manager\Memory Management
"SecondLevelDataCache"= 0 REG_DWORD
Meaning that you paid good money for the processors with extra cache but the operating system is not using it. In some of Microsoft's Q articles they state no performance increase will be seen from setting this value correctly. Most of us in the industry wonder, "Why have the entry then?" In almost every case I have seen of a server running hot on the processor side, we were able to increase performance by setting this value to the actual size of the cache in K.
To do this, open the entry in Regedit or Regedt32 (see Figure 1, below, for instructions) and set this entry to the decimal value of your cache in K. For example, if you have 1 MB worth of L2 cache on each processor this needs to be set at 1024. (NOTE: Do not add up all the processors cache as a total -- it should be the value of cache on the individual processors.)
TIP2: Disable Paging of the Windows NT Executive
Win2K (and NT, too) uses a swap file. We all know this. It takes blocks of memory, or pages, and writes them out to the hard disk to free up physical RAM for other applications or system processes needing memory. No big deal here.
But the Win2K system will also page out some of its own kernel code and drivers to the hard disk. Sounds funny, doesn't it? This was originally intended for machines with limited amounts of RAM, allowing the system to free up memory for applications to use. But on a system with at least 128 MB, you can stop this from happening. How does this help you? Servers running as terminal servers tend to have large amounts of RAM (well over 128), and will see an increase in operating system performance by stopping this paging of the Windows Executive.
Note that Microsoft articles tend to conflict with each other on this item. In article Q184419, Microsoft states that this may "decrease the response time on systems with large amounts of RAM." Interesting. Compare this to its "Instant Rules of Thumb for Tuning and Sizing NT Server" paper, where it states the exact same procedure will result in a performance increase on servers with large amounts of RAM.
I have almost always seen a performance boost on the operating system side when this is done, and believe it's worth it. To stop paging the NT Executive, set the following registry entry:
HKEY_LOCAL_MACHINE\System\Current Control Set\Control\Session Manager\Memory Management
"DisablePagingExecutive"= 1 REG_DWORD

temp2 [ Konsul ]

To mopze taki tip:

Increase BROADBAND:

this ones simple:
this is for broad band connections. I didn’t try it on dial up but might work for dial up.
1.make sure your logged on as actually "Administrator". do not log on with any account that just has administrator privileges.
2. start> run>type gpedit.msc
3. expand the "local computer policy" branch
4. expand the "administrative templates" branch
5. expand the "network branch"
6. Highlight the "QoS Packet Scheduler" in left window
7. in right window double click the "limit reservable bandwidth" setting
8. on setting tab check the "enabled" item
9. where it says "Bandwidth limit %" change it to read 0
reboot if you want to but not necessary on some systems your all done. Effect is immediate on some systems. some need re-boot. I have one machine that needs to reboot first, the others didn't. Don't know why this is.

This is more of a "counter what XP does" thing. In other words,
XP seems to want to reserve 20% of the bandwidth for its self.
Even with QoS disabled, even when this item is disabled. So why not use it to your advantage.

29.03.2003

22:40

[6]

Iceman_87th [ Generaďż˝ ]

ntroot--> zwracam honor :) Mozesz podac zrodlo?

29.03.2003

23:45

[7]

MasterDD [ :-D ]

ntroot => Ten L2 Cache na procq winshit juz mial mi ustawione ,widocznie go wykryl, a siedze na WinXP SP1.
Procek = A XP 2000+

temp2 => Zauwazylem to ograniczenie, qrcze, ciekawe czemu to goofno mialo 20%.

Zaraz zlookam jaki przyrost bedzie :D

30.03.2003

09:52

[8]

yazz_aka_maish [ Legend ]

2 pytanka.

1. Czy w DisablePagingExecutive też dać wartość w systemie dziesiętnym? Bo dałem w 16-kowym.
2. Jaką wielkość L2Cache ma Thunderbird 900Mhz (256 bodajże ale pewności nie mam)

Za odpowiedzi z góry dziękuję :)

temp2 [ Konsul ]

ad.2 Thunderbird 900 ma 256 kb...Wiem bo mam :P