It's not the Load USN Journal in into recent changes option.Hmm, I still(1399a) get delayed ability to query the db on startup. Is it because I use the USN loading feature?
It's caused by the complex result omission filters.
The result omissions are not stored in your database.I do use complex omissions, but isnt the old omissions db stored somewhere ready to get used on startup?
The result omissions filters are stored in your Everything.ini
They need to be re-applied each time you start Everything.
I will consider saving 'applied' result omissions filters to your Everything database.
I could (and should) also make applying the result omissions filters multithreaded..
Thanks for the suggestion.
Everything shouldn't be doing a reindex on startup.(I always wanted to report this as a wish, ie why E doesn't work on startup with the old db until it builds the new one (with some temporarily increased RAM usage). Then I noticed it was one of v1.5 features so I was always thinking this was a problem in my config.)
Please send your Tools -> Debug -> Statistics -> Build -> Last Rebuild Reason
Statistics: Posted by void — Mon Sep 08, 2025 10:44 pm
