Start 10 CPU usage when creating/deleting files

Hello,

I have an issue since years where I just found out why it happens and when.

It seems that when lots of files are created or deleted, the Start10 thread starves CPU cores.

A very simple way to reproduce the issue is to compile a somewhat big project where GCC will create and use temporary files. Then start10 will starve 1-2 threads on my 2 Core (4 Threads) laptop. Basically it shoots up the explorer.exe usage to 40-50% average.

That happens even if I have the project folder in search exclusions in windows search settings and windows defender.

Here's a screenshot from procexp

 

Because of how it happens, my compilations take more than triple the time, even if the cores starved are half or so which is a major issue.

Is there a way to fix this or mitigate it at least?

 

PS: I tried using the start10/11 uninstaller and cleaner tool and reinstalling latest version. And also I tried rebuilding windows search indexer cache. 

8,004 views 4 replies
Reply #1 Top

Where are your files being created?

This looks like Start10 is being notified that files are being changed in one of the folders it monitors for changes but this is limited to the desktop folder, recent files, the start menu folders and the quicklaunch folders.

+1 Loading…
Reply #2 Top

It's in a desktop folder.

So a way to mitigate that is to just move my project files out of desktop, correct?

Reply #3 Top

Quoting ph0en1xv3, reply 2

It's in a desktop folder.

So a way to mitigate that is to just move my project files out of desktop, correct?
End of ph0en1xv3's quote

Yes that seems like it would resolve the problem.

+1 Loading…
Reply #4 Top

Thanks for the fast answer and actually deducting the issue immediately.

I didn't know which folders it parsed and I tried to move it out of desktop and fixed the cpu usage problem.

I would consider that resolved.

 

On the other hand, is it possible to consider an exclusion list feature in the future?

I normally copy the latest projects to desktop because it suits my use case for faster access.