Indexing properties - "best practice" - Every Startup complete scan

Discussion related to "Everything" 1.5 Alpha.
Post Reply
catweazle
Posts: 6
Joined: Mon Jan 09, 2023 4:58 am

Indexing properties - "best practice" - Every Startup complete scan

Post by catweazle »

Hej there,

is there a "best practice" setting up the indexing the properties of files?

I have many files mp4/mp3/jpg/CBr. Actually I configured everything (1333a) for indexing a bunch of properties like artist, album, dimension, fps, ... which seems to work basically pretty nice.

The desired NAS shares are defined within the Database-Folders section, each with:
- index subfolders checkmarked
- monitor changes checkmarked
- buffer size raised to 1024 and
- never rescan

NTFS-Volumes:
- include in Database checkmarked
- Enable USN-Journal checkmarked
- maximum size 32768
- allocation delta 8192
- load USN journal into the Recent Changes Database checkmarked
- monitor changes checkmarked

My point is, that everytime my PC has started Everything seems to scan every defined source once again and again, needing some hours - and for me it would be right perfect just having one initial complete scan and afterwards only monitoring changes.
What am I doing wrong? With 1.4 I got this working like that..
void
Developer
Posts: 15654
Joined: Fri Oct 16, 2009 11:31 pm

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by void »

Everything should index your files and properties once.

What is the last rebuild reason reported under Tools -> Debug -> Statistics -> Build -> Last Rebuild Reason?

Please make sure Everything is installed correctly and running as a standard user:
  • In Everything, from the Tools menu, click Options.
  • Click the General tab on the left.
  • Check Store settings and data in %APPDATA%\Everything.
  • Uncheck Run as administrator.
  • Check Everything Service. (Please make sure this is tick-checked and not square-checked)
  • Click OK.
  • Exit Everything (right click the Everything tray icon and click Exit).
  • Restart Everything.

- buffer size raised to 1024 and
Please only use the default here.
NAS shares do not support values higher than 64KB:
  • In Everything, from the Tools menu, click Options.
  • Click the Folders tab on the left.
  • Change Buffer size to: 64 KB.
  • Click OK.
I would recommend rescanning every day.
This will only rescan your filenames.
Indexed properties are only rescanned for files if the size/date-modified changes.


- load USN journal into the Recent Changes Database checkmarked
Please leave load USN journal into the Recent Changes Database disabled.
Enabling will hurt loading performance on startup.

Only enable this option if you are sorting by "Date Recently Changed" and want access to the changes in the USN Journal.
catweazle
Posts: 6
Joined: Mon Jan 09, 2023 4:58 am

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by catweazle »

Hej Void,

thanks for your fast answer!

- last rebuild reason is "Structure changed"
- "General settings" already as described, completely
- Buffer size changed to 64
- unchecked that USN-Journal setting

The reason why I generally wouldn't need a fix every day rescan is, that I do not have too many changes. I hope to get that changes by "monitor changes". Those daily rescans will take always about 2 hours
But actually, as "never rescan" is being chosen, from my point of view the only consequence should be, that properties or file changes in general wouldn't be reflected within everything.
catweazle
Posts: 6
Joined: Mon Jan 09, 2023 4:58 am

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by catweazle »

and still running indexing...

forgot to switch of pc yesterday, ran through the whole night. Still indexing, or again, don't know...

"Last Build date: 11.01.2023 06:48"
"Last Build reason: Out of date Index is available"

could cause depend on scanning properties of files? With 1.4 I didn't have that problem.
void
Developer
Posts: 15654
Joined: Fri Oct 16, 2009 11:31 pm

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by void »

Could you please send your Tools -> Debug -> Statistics to support@voidtools.com

This information should help identify which volume is being rebuilt and possibly why..

I'm guessing there was a lot of changes to this volume and the USN Journal ID is being changed.
catweazle
Posts: 6
Joined: Mon Jan 09, 2023 4:58 am

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by catweazle »

Hej Void,

sent the desired information last weekend, actually indexing runs on all reachable drives again, "Statistics" states "Structure changed".

Seems that reindexing runs every 2 days, regardless what is configured (Yesterday nothing happened)
void
Developer
Posts: 15654
Joined: Fri Oct 16, 2009 11:31 pm

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by void »

Thanks for the debug logs catweazle,

I have found the issue most likely causing the trouble.

The property system properties are not sorted correctly.
The order changes randomly.
Everything will sometimes see the different order as a change in indexed properties.

I'll have a fix soon.

For now, please try removing your property system properties.
For example:
property-system:System.Comment (Comments)
property-system:System.Keywords (Tags)
property-system:System.Music.Artist (Contributing artists)
property-system:System.Software.NullPreview.Title (Title)
property-system:System.Title (Title)



More discussion here
catweazle
Posts: 6
Joined: Mon Jan 09, 2023 4:58 am

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by catweazle »

Hej Void,

thanks for your assistance! Looking forward to that version :)

regards, Catweazle
void
Developer
Posts: 15654
Joined: Fri Oct 16, 2009 11:31 pm

Re: Indexing properties - "best practice" - Every Startup complete scan

Post by void »

Everything 1.5.0.1336a fixes an issue with Everything reindexing properties when indexing a property system property.

Thank you for your help with finding the issue.
Post Reply