Compile on a Windows XP-Based Computer Takes Longer to Complete Than on a Windows NT-based Computer

Interesting and surely useful KBA on the Microsoft Knowledge Base

SYMPTOMS

When you try to compile a program on a Windows XP-based computer, it may take approximately 30% to 40% longer to complete than it did when the same computer hardware was Windows NT-based.

CAUSE

This problem may occur if you compile a large program that has many files. Windows XP caches the files that you are compiling, and when the Windows cache limit is reached, Windows removes the files from the cache. When it does so, Windows may remove the files that are used frequently during the compilation. To use these files, you must cache them again. Recaching the files slows the compile process.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows XP service pack that contains this fix.

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To successfully apply this hotfix, you must add the ScavengerTimeLimit value to the registry. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters

  3. Right-click Parameters, point to New, and then click DWORD value.
  4. Type ScavengerTimeLimit, and then press ENTER, to name the new value.
  5. Double-click ScavengerTimeLimit.
  6. In the Value data box, type 60, and then click OK.
  7. Close Registry Editor.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
 

No Comments