[Bug]: Windows Search Indexer keeps running when there is no edit action

wdhongtw commented 8 months ago

Confirmation

[X] I checked FAQ

The tool/kit where the error occurred

joplin-vscode-plugin

Describe the bug

Every time when I have this extension enabled in VS Code, the Search Indexer keep consuming CPU resources, even when I do not opening any note in VS Code.

Based on the output of process monitor, it seems that this extension will trigger Joplin to append log to log file, and trigger the action in Search Indexer indirectly.

I'm not sure this can be considered as a bug by this extension, but this phenomenon do bother me a little. :(

I'm wordering if there is anything we can do to reduce the CPU consumption of Search Indexer when using extension?

Environment:

Joplin: v2.14.19
Extension: v1.4.1

Steps to reproduce the behavior

Install this extension and setup the access token
Open Joplin and VS Code with this extension enabled

log file

The error log contains no content.

Additional context

No response

rxliuli commented 8 months ago

Yes, the extension will call the Joplin Webclipper's API to refresh the note tree in VSCode, but I didn't know there would be such an obvious waste of performance on Windows... Maybe, I guess you can temporarily solve this by excluding this directory from the Windows search index?

ref: https://learn.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/windows-search-performance-issues#:~:text=Exclude%20folders&text=To%20exclude%20whole%20folders%20from,Windows%20%3E%20Add%20an%20excluded%20folder.

wdhongtw commented 8 months ago

Thanks for your quick response!

you can temporarily solve this by excluding this directory from the Windows search index

This is a resonable solution, and it do works for me. (I add C:\Users\<username>\.config folder)

I think I should close this issue now... If we need to do something, we can open this issue later. :D

rxliuli / joplin-utils