[Solved] Everything64.exe priority

Discussion related to "Everything" 1.5 Alpha.
Post Reply
w64bit
Posts: 253
Joined: Wed Jan 09, 2013 9:06 am

[Solved] Everything64.exe priority

Post by w64bit »

I noticed that if I copy several large files on a SSD (NTFS) and during copy I open Everything, the copy operation is bring to zero slowly but Everything is frozen trying to index.
There are approx 100 files in SSD so the indexing should be instant.
The freeze it seems to be because of the copy operation.
If I start Everything with high priority will solve this problem?
If yes, is there any Everything setting to use in order to launch every time the program with high priority and to avoid creating a shortcut:
cmd.exe /c start "Everything" /High "C:\Program Files\Everything\Everything64.exe"
Last edited by w64bit on Fri Jan 21, 2022 3:28 pm, edited 1 time in total.
void
Developer
Posts: 16735
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything64.exe priority

Post by void »

What program are you using to copy the large files?

It sounds like something is spam-flushing the file.
This will flood the USN Journal with entries. (and is also very bad for SSDs)
Check your Index -> Journal

Changing the priority of Everything is unlikely to help.

What is shown under Tools -> Debug -> Statistics -> Last Rebuild Reason?


Are you indexing properties under Tools -> Options -> Indexes -> Properties? -Maybe Everything is constantly trying to reread properties for this file?
w64bit
Posts: 253
Joined: Wed Jan 09, 2013 9:06 am

Re: Everything64.exe priority

Post by w64bit »

Everything 1.5.0.1290a x64.
File Explorer Win 10 x64 21H2.
No Property index.

I'll try to replicate and find info for:
- Index -> Journal
- Tools -> Debug -> Statistics -> Last Rebuild Reason
void
Developer
Posts: 16735
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything64.exe priority

Post by void »

Check disk IO with the Microsoft Resource Monitor. -Is Everything reading the disk? Is something else reading/writing to the disk?
Check the smart data on your SSD, make sure there's no reallocated sectors.
w64bit
Posts: 253
Joined: Wed Jan 09, 2013 9:06 am

Re: Everything64.exe priority

Post by w64bit »

only these are reading/writing the disk:
Everything
System (I think this is File Explorer copy operation)

Last Rebuild Reason = Add NTFS volume
SSD with no reallocated sectors

Everything Service = OFF
Launched from administrator account
w64bit
Posts: 253
Joined: Wed Jan 09, 2013 9:06 am

Re: Everything64.exe priority

Post by w64bit »

The copy speed during testing this issue is 450 MB/s on this SATA 3 SSD.
Maybe it's no enough bandwidth left during the copy operation in order to let Everything do the indexing.
void
Developer
Posts: 16735
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything64.exe priority

Post by void »

Did you find anything suspicious in Everything -> Index -> Journal?

Sounds like a concurrency issue.
I have no concurrency issues with my SSD which makes this difficult to troubleshoot..

Everything doesn't have much control over disk access priority.
I will add a index_thread_priority ini setting for the next alpha update.
You'll be able to set background thread priority with this, which will prevent Everything from accessing the disk when it is busy.
I'll reply to this post when this is ready..

USB storage devices generally have no concurrency support.
Is this a USB attached SSD?



When you say Everything freezes, does the UI freeze? or does Everything just get stuck showing indexing in the status bar?
-If the UI freezes it might indicate an issue with a shell extension (eg: accessing icons)


Do you have a lot of files in system cache?
-If so, Everything and the system can hang for several seconds when Everything opens a volume for indexing.
-This issue is made worse when you have millions of files in system cache.
w64bit
Posts: 253
Joined: Wed Jan 09, 2013 9:06 am

Re: Everything64.exe priority

Post by w64bit »

Nothing suspicious in Everything -> Index -> Journal
SSD is USB attached.
I cleaned the system cache. Now, Everything just get stuck showing indexing in the status bar.
You nailed it. It's a concurrency issue for an USB attached drive/SSD.
Post Reply