After an index rebuild, I use utility to check if Everything's .DB file is fragmented. In my case, the .DB file can be in as many as 20 fragments!
Does Everything load the .DB file only at startup or does it access the .DB file for each query?
Fragmentation of Everything's .DB file
Re: Fragmentation of Everything's .DB file
I believe it's on start up.
Then all is done in memory.
Only written back to disk when you quit.
(Mine a different instance from my normal, non-NTFS, is dated 1-28-19 & has 19 frags. 19 or 20 isn't much, IMO.
So that means it was... updated on that date. Though yesterday, I did run a Force Rebuild on it, so once I quit out of that, suppose it will then be dated when I quit.
My regular Profile, oh, that's throwing me for a loop - at the moment.
I'm not sure where it is?
It has to be named, everything.db, & it should be in my Everything (/Locate/) directory, but it is not?
Maybe I'll quit & see what turns up...
> It has to be named, everything.db, & it should be in my Everything (/Locate/) directory, but it is not?
Yep. 22 frags, dated today.
I think I know why it wasn't there... no but that doesn't seem right either...?
Was thinking that I might not have Quit since I installed .924.
And that might be OK - except that there should have been some prior .db from the earlier version of Everything still laying around... which .924 would have started with...
?)
Then all is done in memory.
Only written back to disk when you quit.
(Mine a different instance from my normal, non-NTFS, is dated 1-28-19 & has 19 frags. 19 or 20 isn't much, IMO.
So that means it was... updated on that date. Though yesterday, I did run a Force Rebuild on it, so once I quit out of that, suppose it will then be dated when I quit.
My regular Profile, oh, that's throwing me for a loop - at the moment.
I'm not sure where it is?
It has to be named, everything.db, & it should be in my Everything (/Locate/) directory, but it is not?
Maybe I'll quit & see what turns up...
> It has to be named, everything.db, & it should be in my Everything (/Locate/) directory, but it is not?
Yep. 22 frags, dated today.
I think I know why it wasn't there... no but that doesn't seem right either...?
Was thinking that I might not have Quit since I installed .924.
And that might be OK - except that there should have been some prior .db from the earlier version of Everything still laying around... which .924 would have started with...
?)
Re: Fragmentation of Everything's .DB file
To clarify, the entire db is loaded into memory on startup.
The entire database is re-written to disk when you exit Everything.
How large is your Everything.db and how much free space do you have?
There is a compress database on disk option which may help.
However, it does reduce the start and exit performance of Everything.
The Everything.db file location can be customized.
It is usually saved as %LOCALAPPDATA%\Everything\Everything.db
You can use a custom filename with the -db command line option.
The entire database is re-written to disk when you exit Everything.
How large is your Everything.db and how much free space do you have?
There is a compress database on disk option which may help.
However, it does reduce the start and exit performance of Everything.
The Everything.db file location can be customized.
It is usually saved as %LOCALAPPDATA%\Everything\Everything.db
You can use a custom filename with the -db command line option.
Re: Fragmentation of Everything's .DB file
The fragmentation is caused by the way Everything saves the database to disk:
the database is saved in a temp-file and if that succeeded, that will become the new database (a safety measure also).
Same goes for Everything.ini, btw.
the database is saved in a temp-file and if that succeeded, that will become the new database (a safety measure also).
Same goes for Everything.ini, btw.