is there a good way to diagnose high cpu usage with everything? Lately I will occasionally have it completely use one hundred percent of all my cpu cores (on a 14900ks)
I suspect there is some sort of interaction with https://github.com/lin-ycv/EverythingPowerToys/ As it's usually happening when I'm using power toys run.
diagnose high cu usage
Re: diagnose high cu usage
To show a debug console:
In Everything, from the Tools menu, under the Debug submenu, click Console.
Wait for Everything to use 100% CPU.
What is shown in the debug console?
In Everything, from the Tools menu, under the Debug submenu, click Console.
Wait for Everything to use 100% CPU.
What is shown in the debug console?
Re: diagnose high cu usage
I'm suspecting its an everything power toys issue.
I'm using EPT with the set filter "ccdclauncher" which uses c:\ccdc\portableapps|c:\ccdc\scripts|c:\ccdc\sysinternals|c:\ccdc\avalerts\nirsoft|c:\ccdc\commandlinetools|<c:\users\jolly "start menu">|"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\"|"C:\Users\jolly\Downloads" ext:exe;lnk;cmd;bat;ahk !sync-conflict
I see two issues:
1) the same fast path search lines repeated over and over.
2) Seems like EPT might be sending everything extra old queries.
starting around lines 107222
I created an issue over https://github.com/lin-ycv/EverythingPo ... issues/149
2024-12-18 18:50:20.323: IPC: execute query: filter:ccdclauncher steam
2024-12-18 18:50:20.324: search 'filter:ccdclauncher steam' filter '' sort 5 ascending 0
2024-12-18 18:50:20.324: IPC: wait 2
2024-12-18 18:50:20.325: expanded: < < nofiltercase:filterpath:nofilterwholeword:nofilterdiacritics:nofilterprefix:nofiltersuffix:nofilterignorepunctuation:filterignorewhitespace:nofilterregex:< c:\ccdc\portableapps|c:\ccdc\scripts|c:\ccdc\sysinternals|c:\ccdc\avalerts\nirsoft|c:\ccdc\commandlinetools|<c:\users\jolly "start menu">|"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\"|"C:\Users\jolly\Downloads" ext:exe;lnk;cmd;bat;ahk !sync-conflict > > > steam
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search portableapps
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search portableapps
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search scripts
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search scripts
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search sysinternals
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.326: fast path search sysinternals
2024-12-18 18:50:20.326: fast path search c:
2024-12-18 18:50:20.326: fast path search ccdc
I'm using EPT with the set filter "ccdclauncher" which uses c:\ccdc\portableapps|c:\ccdc\scripts|c:\ccdc\sysinternals|c:\ccdc\avalerts\nirsoft|c:\ccdc\commandlinetools|<c:\users\jolly "start menu">|"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\"|"C:\Users\jolly\Downloads" ext:exe;lnk;cmd;bat;ahk !sync-conflict
I see two issues:
1) the same fast path search lines repeated over and over.
2) Seems like EPT might be sending everything extra old queries.
starting around lines 107222
I created an issue over https://github.com/lin-ycv/EverythingPo ... issues/149
2024-12-18 18:50:20.323: IPC: execute query: filter:ccdclauncher steam
2024-12-18 18:50:20.324: search 'filter:ccdclauncher steam' filter '' sort 5 ascending 0
2024-12-18 18:50:20.324: IPC: wait 2
2024-12-18 18:50:20.325: expanded: < < nofiltercase:filterpath:nofilterwholeword:nofilterdiacritics:nofilterprefix:nofiltersuffix:nofilterignorepunctuation:filterignorewhitespace:nofilterregex:< c:\ccdc\portableapps|c:\ccdc\scripts|c:\ccdc\sysinternals|c:\ccdc\avalerts\nirsoft|c:\ccdc\commandlinetools|<c:\users\jolly "start menu">|"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\"|"C:\Users\jolly\Downloads" ext:exe;lnk;cmd;bat;ahk !sync-conflict > > > steam
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search portableapps
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search portableapps
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search scripts
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search scripts
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.325: fast path search sysinternals
2024-12-18 18:50:20.325: fast path search c:
2024-12-18 18:50:20.325: fast path search ccdc
2024-12-18 18:50:20.326: fast path search sysinternals
2024-12-18 18:50:20.326: fast path search c:
2024-12-18 18:50:20.326: fast path search ccdc
Last edited by void on Thu Dec 19, 2024 1:38 am, edited 1 time in total.
Reason: removed log
Reason: removed log
Re: diagnose high cu usage
Thank you for the logs.
-use ext:exe;lnk;cmd;bat;ahk first as this will reduce the number of path lookups.
-Add a trailing \ to your paths
This will improve search performance.
The trailing slash causes Everything to match against a complete folder path.
Whereas no trailing slashes causes Everything to build full paths and perform a search (c:\ccdc\portableapps could match c:\ccdc\portableapps and c:\ccdc\portableapps2 )
-Place your search before the filter:ccdclauncher term.
For example:
Does the high CPU usage persist?
Please try changing your ccdclauncher filter search to:Code: Select all
2024-12-18 18:50:51.651: 000000004edacc88 20f00104 M 000000004edadaf8 N 00000000606d55a8 OP 514 c:\ccdc\portableapps 2024-12-18 18:50:51.651: 00000000606d55a8 20f00104 M 000000004edadaf8 N 000000004edae578 OP 514 c:\ccdc\scripts 2024-12-18 18:50:51.651: 000000004edae578 20f00104 M 000000004edadaf8 N 000000004edad318 OP 514 c:\ccdc\sysinternals 2024-12-18 18:50:51.653: 000000004edad318 20f00104 M 000000004edadaf8 N 000000004edac748 OP 514 c:\ccdc\avalerts\nirsoft 2024-12-18 18:50:51.653: 000000004edac748 20f00104 M 000000004edadaf8 N 00000000606d5828 OP 514 c:\ccdc\commandlinetools 2024-12-18 18:50:51.653: 00000000606d5828 20f00104 M 00000000606d6368 N 000000005eea78c8 OP 514 c:\users\jolly 2024-12-18 18:50:51.653: 00000000606d6368 a0f00104 M 000000004edadaf8 N 000000005eea78c8 OP 41 start menu 2024-12-18 18:50:51.653: 000000005eea78c8 a0f00104 M 000000004edadaf8 N 000000004edad708 OP 514 C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ 2024-12-18 18:50:51.653: 000000004edad708 a0f00104 M 000000004edadaf8 N 0000000000efe860 OP 514 C:\Users\jolly\Downloads 2024-12-18 18:50:51.653: 000000004edadaf8 20f00104 M 00000000606d6868 N 0000000000efe860 OP 197 exe;lnk;cmd;bat;ahk 2024-12-18 18:50:51.653: 00000000606d6868 20f18504 M 0000000000efe860 N 00000000606d56e8 OP 41 sync-conflict 2024-12-18 18:50:51.654: 00000000606d56e8 20e00104 M 0000000000efe980 N 0000000000efe860 OP 308 memory
ext:exe;lnk;cmd;bat;ahk !sync-conflict c:\ccdc\portableapps\|c:\ccdc\scripts\|c:\ccdc\sysinternals\|c:\ccdc\avalerts\nirsoft\|c:\ccdc\commandlinetools\|<c:\users\jolly\ "start menu">|"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\"|"C:\Users\jolly\Downloads\"
-use ext:exe;lnk;cmd;bat;ahk first as this will reduce the number of path lookups.
-Add a trailing \ to your paths
This will improve search performance.
The trailing slash causes Everything to match against a complete folder path.
Whereas no trailing slashes causes Everything to build full paths and perform a search (c:\ccdc\portableapps could match c:\ccdc\portableapps and c:\ccdc\portableapps2 )
-Place your search before the filter:ccdclauncher term.
For example:
memory filter:ccdclauncher
Does the high CPU usage persist?
This is normal.1) the same fast path search lines repeated over and over.
Re: diagnose high cu usage
Thanks, that's good to know about the efficiency improvements.
the root cause seems to be that Microsoft's power toys run history feature will pass historical results to the plugins to check if its still valid. So it passes it to EverythingPowerToys, which passes it to Everything.
"In order to make sure selected results in the history are still valid, we re-query the plugin the relevant plug using the PluginManager. If there are no results, this history item is not included. This usually means that the result is no longer valid. For instance, if a file was deleted, but it's still in the selected history we don't want to show it as a selectable result.
Because the results from the History Plugin are actually created from calls to the PluginManager, they will be exactly the same is if they did not come from the History Plugin."
the root cause seems to be that Microsoft's power toys run history feature will pass historical results to the plugins to check if its still valid. So it passes it to EverythingPowerToys, which passes it to Everything.
"In order to make sure selected results in the history are still valid, we re-query the plugin the relevant plug using the PluginManager. If there are no results, this history item is not included. This usually means that the result is no longer valid. For instance, if a file was deleted, but it's still in the selected history we don't want to show it as a selectable result.
Because the results from the History Plugin are actually created from calls to the PluginManager, they will be exactly the same is if they did not come from the History Plugin."
How does this impact things?-Place your search before the filter:ccdclauncher term.
For example:
memory filter:ccdclauncher