Pause monitor

Discussion related to "Everything" 1.5 Alpha.
Post Reply
NotNull
Posts: 3152
Joined: Wed May 24, 2017 9:22 pm

Pause monitor

Post by NotNull » Thu Jun 10, 2021 12:51 pm

v 1261a (x64)

After a /monitor_pause :

Code: Select all

read usn journal C: in 0.012568 seconds
[..]
PIPE WRITE 35 20
READ 8
READ 79
PIPE READ 0 87
updated C: in 0.002894 seconds
resume ntfs monitor 0
Is 'read usn journal C:' expected when monitors are paused?

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

Re: Pause monitor

Post by void » Sun Jun 13, 2021 7:28 am

Sorry for the delay in my reply, I didn't get a notification for your post... weird..

Currently:
If pause index updates is enabled on startup, the USN Journal monitors are not started.
If the monitors are already started, pausing index updates them will keep them running.
Changes will be detected, but your index will not be updated until you unpause or exit Everything.


This could be undesirable if you expect Everything to not make any changes to the index on exit while the index is paused.
The next alpha update will stop the USN Journal monitors and process any pending changes to the index when pausing updates.


Folder monitors will continue to watch for changes (even when paused), otherwise Everything could become out-of-date.
Changes to your folder indexes are not made until you unpause or exit Everything.

NotNull
Posts: 3152
Joined: Wed May 24, 2017 9:22 pm

Re: Pause monitor

Post by NotNull » Sun Jun 13, 2021 10:17 pm

Thanks for the info!

I don't think many people will have a serious need to halt the monitors in 1.5. Especially since index updates are non-blocking now.


The reason I did pause the monitors has an entirely different reason: "noise-cancelling": to filter out irrelevant entries - for that specific case - in the debug view.
So not a big deal (to me) as most entries were relevant now. Just curious. As usual ... :)

Post Reply