void wrote: Tue May 05, 2026 12:58 am
Everything doesn't have any native avif support.
Reading any properties will go through the Windows Property System.
What properties are you reading?
Third party avif property handlers can be installed.
There might be faster property handlers out there.
Enabling multiple threads for your volume index might help:
- In Everything 1.5, from the Tools menu, click Options.
- Click the NTFS, FAT, ReFS or folders tab on the left. (the one that indexes your volume with the avif files)
- Right click your volume and under Advanced, under the Threads submenu, check Multiple threads.
Note enabling might make performance worse for some hard drives.
It is only avif that is slow, threads wouldn't matter as it's otherwise much faster and it doesn't go near 4% anyway and each thread is 8%. The one for audio and video is set to 2 threads and regularly sits at 13-16% as it should and so does the image one when it's not touching avif. It's almost done with known avif, so in a week or 2 it might finally work at normal speed again...Presuming there aren't a lot of avif files with other extensions.
Here is the ini's list, essentially all audio, video and stills properties or hopefully all of those.
properties=35mm Focal Length,Album,Album Artist,Altitude,Aperture,Artist,Aspect Ratio,Audio Bit Rate,Audio Bits Per Sample,Audio Channels,Audio Format,Audio Sample Rate,Audio Track Count,Author URL,Authors,Beats Per Minute,Bit Depth,Brightness,Camera Maker,Camera Model,Camera Serial Number,Color Representation,Comment,Composer,Compressed Bits Per Pixel,Compression,Conductor,Content Provider,Contrast,Copyright,Date Acquired,Date Encoded,Date Released,Date Taken,Description,Digital Zoom,Dimensions,Director,Encoded By,Exif Version,Exposure Bias,Exposure Program,Exposure Time,F-Stop,File Signature,Flash Energy,Flash Maker,Flash Mode,Flash Model,Focal Length,Frame Count,Frame Rate,Genre,Group Description,Height,Horizontal Resolution,Image ID,Initial Key,ISO Speed,Latitude,Length,Lens Maker,Lens Model,Light Source,Longitude,Maker Note,Max Aperture,Metering Mode,Mood,Orientation,Parental Rating,Parental Rating Reason,Part of a Compilation,Part of Set,People,Period,Photometric Interpretation,Producer,Promotion URL,Protected,Publisher,QuickTime Metadata,Rating,Related Sound File,Resolution Unit,Saturation,Sharpness,Shutter Speed,Size on Disk,Software,Subject,Subject Distance,Subtitle,Subtitle Track Count,Tags,Title,Total Bit Rate,Track,Transcoded For Sync,Vertical Resolution,Video Bit Rate,Video Format,Video Track Count,Vorbis Comment,White Balance,Width,Writer,Year
I haven't touched property handlers yet, other ones at least. Maybe I should bother looking that sort of solution up. There is one benefit to the slowness and that's the low CPU usage. It works well for most activities, even CPU-heavy games. But it takes maybe 2 minutes for one file. If that was the speed, it would probably take literal years to finish all 5mil.
If my math doesn't suck, it would be 19-20 years. It's already done 7.4mil files and that's in less than 2 months because the folder for the instance is less than 2 months old. So avif has caused a proper crawl, hehe.
It would be faster to read files at normal speed and pause whenever I'm playing video games or using heavier Firefox sessions and resume when not. That's what I do for the audio/video instance and it's done at least 100K files in the same time as 15K avif files when the stills instance is rarely paused. I will likely look at property handler changes if known avif are done and it's still crawling at avif files with other extensions as there is no way for me to know how many of those I have..I presume. Reading the properties in the first place with EBV is one way but then I've already read them.
...But that's already the case, I don't limit every program so programs that are free to use any threads, particularly system components, will already be fighting over the first few threads as I understand it Windows goes from thread 0 to max when assigning work.
.