USN and .db

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
harryray2
Posts: 100
Joined: Sat Oct 15, 2016 9:56 am

USN and .db

Post by harryray2 » Sun Feb 05, 2017 10:23 am

Just a couple of general questions:

Is there any advantage to including the USN journal (whatever that is!) in recent changes?
How does the everything.db file work? It only seems to update every so often.

Tnanks

void
Site Admin
Posts: 4449
Joined: Fri Oct 16, 2009 11:31 pm

Re: USN and .db

Post by void » Sun Feb 05, 2017 10:31 am

Is there any advantage to including the USN journal (whatever that is!) in recent changes?
Enabling Include USN Journal in recent changes will load the entire USN Journal into the recent changes list when Everything is started.
The USN Journal is a record of all file changes for about a week (varies greatly on file system usage).
You can search recent changes with the rc: search function.

Useful in Everything 1.3 if you use recent changes (searching with rc:)
In Everything 1.4 or later it's not very useful as date modified information is indexed for all files. (searching with dm:)

Loading the entire USN Journal can be expensive when starting Everything.
It is recommend that you leave this option disabled in Everything 1.4 or later.
How does the everything.db file work? It only seems to update every so often.
Everything keeps the entire Everything index in memory while Everything is running.
The Everything index is only saved to the Everything.db when you exit Everything.

SuperDude
Posts: 96
Joined: Thu Sep 25, 2014 7:57 pm

Re: USN and .db

Post by SuperDude » Mon Feb 06, 2017 12:08 am

@void: When you recommend that we disable the "Include USN Journal in recent changes," do you mean we should disable it for each volume that Everything indexes? Everything will still catch changes to monitored drives, yes? Does that option exist just for compatibility with older versions of Everything?

void
Site Admin
Posts: 4449
Joined: Fri Oct 16, 2009 11:31 pm

Re: USN and .db

Post by void » Mon Feb 06, 2017 12:18 am

do you mean we should disable it for each volume that Everything indexes?
Yes, disable it for each volume.
It should be disabled by default.
Everything will still catch changes to monitored drives, yes?


Yes, Everything will continue to monitor changes as long as Monitor changes is checked.

The option for Include USN Journal in recent changes is to allow the user to efficiently find more recent changes when indexing date modified information is disabled. If indexing date modified information is enabled, there is little point to using recent changes.

Recent changes is slightly more efficient than indexing date modified information, however, the usefulness of indexing all date modified information out ways any performance loss or extra memory usage, both of which is negligible.

Post Reply