3 ms·
'winmgmt.exe /verifyrepository', the tool with the O(n^2) behavior, is a diagnostic tool-- it verifies the consistency of the WMI repository.
by JonathonW 7y ago
'winmgmt.exe /verifyrepository', the tool with the O(n^2) behavior, is a diagnostic tool-- it verifies the consistency of the WMI repository.
- Someone1234 7y agoHe used that to manually reproduce, but the original behaviour wasn't caused by manually calling the winmgmt executable with the /verifyrepository switch. Instead the repo was being verified as a side effect of another WMI operation.
- tedunangst 7y agoIt sure sounded like they had a scheduled task to run it manually every hour. "Until then our IT department has promised to stop running the /verifyrepository command every hour, which should avoid the worst symptoms."
- brucedawson 7y agoI believe that the repo gets verified automatically as a daily thing, but our IT department was verifying it hourly. They have stopped. I think that the hourly verification was put in to try to diagnose some problems that were actually or suspected to be related to WMI corruption. Even daily verification is going to cause problems, they are just less likely to be noticed, until they get to the 30+ minutes level.
- ComputerGuru 7y agoThat’s just a manifestation of the issue and not necessarily the only symptom. Dawson used it to explicitly illustrate the wbem size to slowdown effect. The reason I’m hating on developers that use WMI when alternatives are available is because WMI is dog slow and everyone that does low-level Windows development knows it.