Assume Everything is installed and running. Also that volumes have been added and removed, and different indexing options have been changed.
Will it improve Everything's performance to delete the database file and re-index everything from scratch?
I have a hunch that just re-indexing after a lot of changes might cause the database to "inherit" some old data or old structures which might not be completely efficient.
Re-creating the database for performance?
Re: Re-creating the database for performance?
In general it should not be necessary to re-create the database.
When Everything exits, the database is restructured to save it as efficient as possible.
However ...
When the datbase gets bigger, it will take Everyting (a little) more time to fetch the results. Tha's normal behaviour.
So when you have a lot of - for example - external disks / USB sticks that you no longer use / are eaten by your dog / .. , you can consider removing them from the database.
Deleting the database is one way to do so (but be prepared to attach all the external disks that you *do* want to keep in the database), but there is a less rigorous way:
When Everything exits, the database is restructured to save it as efficient as possible.
However ...
When the datbase gets bigger, it will take Everyting (a little) more time to fetch the results. Tha's normal behaviour.
So when you have a lot of - for example - external disks / USB sticks that you no longer use / are eaten by your dog / .. , you can consider removing them from the database.
Deleting the database is one way to do so (but be prepared to attach all the external disks that you *do* want to keep in the database), but there is a less rigorous way:
- Go to Menu:Tools > Options > Indexes > NTFS
- In the list of Local NTFS volumes. click on the disk you want to remove from the index.
- Deselect Include in database
- Click OK
- Repeat this for all volumes you want to remove