About the problem that the resource manager freezes after windows is mapped to samba

After mounting samba for a period of time, the amount of CPU and memory occupied by the resource manager increased rapidly, causing the overall windows system to freeze.

In response to this phenomenon, I did the following steps.

1. Find information, some say it is a problem with the superfetch service and the Microsoft Compatibility Appraiser scheduler

2, try to solve

2.1. Find the superfetch service and find that the new version of win10 does not have this service, give up

2.2. Open Task Scheduler, find Task Scheduler Library-Microsoft-Windows-Application Experience, disable Microsoft Compatibility Appraiser

After setting up 2.2, run it for a while and found that it has almost no effect. .

 

Try again, after consulting the official windows information. Found an important problem: indexing

That is to say, when indexing is enabled by default in Windows, but due to the file structure and file attributes of samba mounted in the development environment, the indexing time may be too long and occupy too many resources.

Find index-related information, most likely caused by the windows search service

Turn off the windows search service in the domain controller.

 

At present, after 2 weeks of testing, the problem of carton has not been found, and it has been solved visually.

{{o.name}}
{{m.name}}

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324104706&siteId=291194637