Debug window messages?

[wkearney99]

I've recently upgraded to 1383a and am noticing that's considerably slower to update attributes. The previous version I'd been using was 1333a.

I'm running on Windows 10 Pro 22H2 19045.4529. It's on an AMD 5900X with 64gb of RAM, so it shouldn't be starved for resources (and wasn't before). EV and all of it's files are running from an SSD. The data being indexed is on a NAS on a 10Gbe network (that's not showing any other signs of speed issues using other software/tests). Both the PC and the NAS have been rebooted after noticing this indexing slowdown (and saw no improvements).

The only additional attributes I'm looking for are height, width and videoformat. I realize digging into the files for the attributes doesn't come without I/O costs. But it sure seems like 1338a (or prior?) was a lot faster at building the indexes.

Is there any documentation that explains some of the messages seen in the Tools->Debug->Console window?

I'm seeing a lot of these and don't believe I'm using files with streams. The volume is a network share on a linux-based NAS (using samba).

Code: Select all

RDC MODIFIED .streams
RDC MODIFIED .streams
RDC MODIFIED .streams
RDC MODIFIED .streams
RDC MODIFIED .streams
RDC MODIFIED .streams
RDC MODIFIED .streams
RDC MODIFIED .streams
getlongpathname 2 \\media\e2k\.streams
getlongpathname pathpart \\media\e2k
FindFirstFileW \\media\e2k\.streams 2
DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waiting for _db_monitor_folder_process_fd_update_events_thread_proc...
DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waited 0.000064 seconds

I cannot post whole logs.

The verbose version of a similar stretch was about 800 lines of text. It's processing what looked to be about 8 files. This is how one file between the RDC MODIFIED lines appeared:

Code: Select all

2024-07-10 09:41:36.244: RDC MODIFIED \\media\e2k\.streams
2024-07-10 09:41:36.244: ReadDirectoryChangesW \\media\e2k  65536
2024-07-10 09:41:36.244: rdc wait 3 0
2024-07-10 09:41:36.264: get property 14 \\media\e2k\06\video1.mp4
2024-07-10 09:41:36.264: get property system property 14 \\media\e2k\06\video1.mp4
2024-07-10 09:41:36.278: get property 18 \\media\e2k\06\video1.mp4
2024-07-10 09:41:36.278: get property system property 18 \\media\e2k\06\video1.mp4
2024-07-10 09:41:36.284: get property 34 \\media\e2k\06\video1.mp4
2024-07-10 09:41:36.284: get property system property 34 \\media\e2k\06\video1.mp4
2024-07-10 09:41:36.289: MSG: 000000000009005e 0113 0000000000000003 0000000000000000
2024-07-10 09:41:36.289: TRAY 00000113 0000000000000003 0000000000000000
2024-07-10 09:41:36.289: MSG OK
2024-07-10 09:41:36.291: get property 13 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.291: get property system property 13 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.312: readdir 28
2024-07-10 09:41:36.313: RDC MODIFIED \\media\e2k\.streams
2024-07-10 09:41:36.313: ReadDirectoryChangesW \\media\e2k  65536
2024-07-10 09:41:36.313: rdc wait 3 0
2024-07-10 09:41:36.337: MSG: 0000000000000000 0113 00000000000047db 00007ff8a86cc460
2024-07-10 09:41:36.337: MSG OK
2024-07-10 09:41:36.337: MSG: 000000000009005e 0113 0000000000000002 0000000000000000
2024-07-10 09:41:36.337: TRAY 00000113 0000000000000002 0000000000000000
2024-07-10 09:41:36.337: statusbar proc 0000040c 0000000000000000 0000000000000000
2024-07-10 09:41:36.337: statusbar proc 0000040d 0000000000000000 00000000009fe9d8
2024-07-10 09:41:36.338: MSG OK
2024-07-10 09:41:36.344: get property 14 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.344: get property system property 14 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.361: get property 18 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.361: get property system property 18 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.370: get property 34 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.370: get property system property 34 \\media\e2k\06\video2.mp4
2024-07-10 09:41:36.379: get property 13 \\media\e2k\06\video3.mp4
2024-07-10 09:41:36.379: get property system property 13 \\media\e2k\06\video3.mp4
2024-07-10 09:41:36.407: readdir 28

I've also noticed considerable slow-down when it comes to seeing thumbnails of images. This may or may not be due to other factors with windows (and it's various updates). To be fair though, the volumes in question have literally tens of thousands of video and image files.

[wkearney99]

I've also noticed the non-verbose mode for attributes barely emits any messages at all. You'd think the indexer was "done" for how 'silent' the debug console appears.

Still, pretty amazing stuff.

I've split some of the network folders into separate indexes to see if that changes things. They're on the same network volume and that used to be the folder that was indexed. Now it's indexing several separate ones within that volume. Don't know if that'll help or not.

[void]

It could be the change in 1342a to favor the Windows Property System over the builtin Everything properties.

Please try disabling the Windows Property System and see if performance improves:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  property
• Select: property_system
• Set the value to: false
• Click OK.

property_system



Are the files changing often?
Maybe it's the new property_read_on_change_delay changes?

To disable the property read delay:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  property
• Select: property_read_on_change_delay
• Set the value to: 0
• Click OK.

Does the slow indexing persist?

[wkearney99]

I'm going to change those now. I'm in the middle of some work so I can't re-index right at the moment. I'll try later tonight.

I do have it set to re-index at 3am, fwtw.

[wkearney99]

Is here a way to tell it to favor local media for indexing first over network folders?

And I suppose I should probably ask what's the difference between using a whole network drive vs using a folder on a network drive?

I have a network share that contains far more files than I want EV to index. Thus I don't index \\someserver\someshare but instead set up a folder \\someserver\someshare\onlythesefiles and \\someserver\someshare\onlythosefiles

Is there some efficiency difference I'm hindering with this?

[void]

Is here a way to tell it to favor local media for indexing first over network folders?

No.
Everything will use separate threads for indexing local properties and indexing network properties.

And I suppose I should probably ask what's the difference between using a whole network drive vs using a folder on a network drive?

There's no difference to Everything.
Both are a folder on the network.
To clarify Tools -> Options -> Network Drive is exactly the same as Tools -> Options -> Folders.
Tools -> Options -> Network Drive just makes it slightly easier to include your volumes in your index. (don't have to click add... -> select drive -> OK)

I have a network share that contains far more files than I want EV to index. Thus I don't index \\someserver\someshare but instead set up a folder \\someserver\someshare\onlythesefiles and \\someserver\someshare\onlythosefiles

Is there some efficiency difference I'm hindering with this?

Indexing only the files you want will help performance and efficiency.
It's faster and more efficient to index more subfolders than to index only the root folder.



Please try setting your folder index to multiple threads (only if your server can handle it):

• In Everything 1.5, from the Tools menu, click Options.
• Click the Folders tab on the left.
• Folder each folder index:
  • Right click the folder index and under the Advanced submenu, under the Threads submenu, click Multiple threads.
• Click OK.