use multiple and optional databases

[Yang]

Hi dear friends,

Is it possible to use multiple and optional databases for the programme?

Situation:

• I's using Windwos 11 PC, and Everything Version 1.5.0.1383a(x64). I have 12 drives to be managed and indexed by Everything, 1 local drive and 11 removable hard disks, all NTFS, and every drive has only one partition.

• The local one is searched very offten but others sometimes. When I use the others, I plug it into the PC.

• So, the Option - Indexes - NTFS option is like this:
  • [ x ] Automatically include new fixed volumes
  • [ ] Automatically include new removable volumes
  • [ ] Automatically remove offline volumes
  • Settings for every volume, [ x ] Include in database

• I index them one by one and all indexes finished and data I need all stored into the database. Then removable drives are all unplugged. Only one volume is online, it's my local drive C:\.

• I use Everything for weeks like this. But everytime when I check the Task Manager of the system, it shows that Everything uses 0.3%~5% of CPU and 800MB~1300MB RAM.

• The database of Everything is 420,398KB.

Question:

• I understand that Everyhing read the database into the RAM when it's running. So is it possible to use multiple and optional databases for differient drives? For example, database1 for C:\, database2 for D:\, E:\, database3 for F:\, G:\..., they are optional to be loaded or unloaded.

• Is there any other method to reduce the CPU and RAM usage?

Thanks.

[void]

is it possible to use multiple and optional databases for differient drives?

Please try named instances

For example:

Everything.exe -instance "Drive 1"
Everything.exe -instance "Drive 2"
Everything.exe -instance "Drive 3 + 4"

Is there any other method to reduce the CPU and RAM usage?

Reduce Ram and CPU Usage of Everything

Disabling the following will make the largest difference:

Tools -> Options -> Indexes -> Index file size
Tools -> Options -> Indexes -> Index date modified
Tools -> Options -> Indexes -> Index recent changes

[Yang]

Please try named instances

Resolved! Thanks void.

[Herkules97]

Also if you care about the index journal, it is advised to make an instance for each device, because when starting a device EBV may sometimes throw a fit and decide the device is different and undo your database's journal.
Another thing can be to save the db with /save-db in the search bar before you start one of the devices or alternatively..
To start the program after starting the device, not sure the recent changes mechanic works if you start the db first. This would prevent a device that is "different" somehow from having the db attached to it re-built and losing changes. Even if it happens, your original db is still intact as EBV is in-ram until a save is made. Just copy the db off before next save happens.

[Yang]

Also if you care about the index journal, it is advised to make an instance for each device, because when starting a device EBV may sometimes throw a fit and decide the device is different and undo your database's journal.
Another thing can be to save the db with /save-db in the search bar before you start one of the devices or alternatively..
To start the program after starting the device, not sure the recent changes mechanic works if you start the db first. This would prevent a device that is "different" somehow from having the db attached to it re-built and losing changes. Even if it happens, your original db is still intact as EBV is in-ram until a save is made. Just copy the db off before next save happens.

Hi Herkules97,

Thanks for your professional reminding and advice. It's indeed a situation of deep use, which I'm not covering yet, but surely it will help in the next if I run into problems then.