Long Time to close Everything?

[nikov]

I also noticed this issue. With 6 million items with the default settings and with the attached Indexes settings, Everything latest alpha takes about 4 seconds (but not 10 minutes that long ) for closing, I tried to mitigate this by force closing Everything with TASKKILL.
But after force closing, Everything seems to work fine.
What can be or what are the side effects of force closing Everything?


Tools -> Debug -> Statistics -> Database -> Total size: 680,008,005 bytes
Everything else is default: i.e. column settings are the default. i.e. What Everything offers when it is first started (only the "Name, Path, Size, Date Modified" columns)


attached Indexes settings:

attached_Indexes_settings.png (24.69 KiB) Viewed 1337 times

[void]

Moved from Long Time to close Everything

That thread is related to Everything taking a long time to process millions of file changes.
I'll have a work around for this in the next alpha update.



Everything stores the entire database in memory.
Everything will save the entire database to disk when you exit Everything.
4 seconds to save a 680MB database to disk is expected.

To disable the save database to disk on exit: (not recommended)

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  save
• Select db_save_on_exit.
• Set the value to: false
• Click OK.

I don't recommend doing this as it will usually take more than 4 seconds to update from your old database on disk.
Everything will still periodically save your database to disk (every day at 4 AM)



Please consider excluding files/folders from your index.

Optimal Settings for Everything

[nikov]

Moved from Long Time to close Everything

That thread is related to Everything taking a long time to process millions of file changes.
I'll have a work around for this in the next alpha update.



Everything stores the entire database in memory.
Everything will save the database to disk when you exit Everything.
4 seconds to save a 680MB database to disk is expected.

To disable the save database to disk on exit: (not recommended)

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  save
• Select db_save_on_exit.
• Set the value to: false
• Click OK.

I don't recommend doing this as it will usually take more than 4 seconds to update your old database on disk.
Everything will still periodically save your database to disk (every day at 4 AM)



Please consider exclude files/folders from your index.

Optimal Settings for Everything

Many thanks, setting `db_save_on_exit=0` closes Everything quickly.
But where does it take more than 4 seconds to update the old database?
I am seeing Everything is working fine as before.

Also, as I have set `db_save_on_exit=0`, I have also set `db_auto_save_type=1` and `db_auto_save_interval=7200000` (2 hours).
Also in your linked page I noticed, default value for `db_auto_save_idle_delay` is 5 minutes but in the Everything program, default is 1 minute.
And I set `db_auto_save_idle_delay` to 5 minutes.
Anything wrong with these changes in settings?


Another question arose by following your solution:
To improve speed, I converted `Result Omissions` to `Index Exclude List` using `Index -> Add Result Omissions to the Index Exclude List`.
But sometime I also need to search in the omission results. To do this, now I have to disable exclude list but then it takes a lot of time to rebuild the index.
This could be solved if I could open a new Everything instance with something like `Index Include List` (opposite of `Index Exclude List`).
Is this possible?


Thank you for your consideration.

[void]

Many thanks, setting `db_save_on_exit=0` closes Everything quickly.
But where does it take more than 4 seconds to update the old database?

When you first start Everything.
Everything will show Updating in the status bar.
This will likely take longer than 4 seconds.
You can continue to use Everything while this update occurs in the background.

Also in your linked page I noticed, default value for `db_auto_save_idle_delay` is 5 minutes but in the Everything program, default is 1 minute.

Thanks for pointing this out.
Updated the ini page to 1 minute.

Also, as I have set `db_save_on_exit=0`, I have also set `db_auto_save_type=1` and `db_auto_save_interval=7200000` (2 hours).
Anything wrong with these changes in settings?

I would recommend using a longer interval.
Please consider every 6-12 hours.

This could be solved if I could open a new Everything instance with something like `Index Include List` (opposite of `Index Exclude List`).
Is this possible?

Fire up a new instance

For example:

Everything.exe -instance "No Excludes"
Setup the same volumes or import your settings from your main instance.

[raccoon]

Everything will still periodically save your database to disk (every day at 4 AM)

Can you avoid scheduling tasks AT 4am (3am, 5am) because everything wants to do their daily routine on that hour. Recommend picking a random minute that doesn't interfere with top-of-the-hour updates, backups, virus scans, end-of-day reports, etc.

[nikov]

Fire up a new instance

For example:

Everything.exe -instance "No Excludes"
Setup the same volumes or import your settings from your main instance.

Thank you, new instance is working fine, but I also need to access files using Everything SDK.
How can I convince Everything SDK to retrieve data from the "No Excludes" instance?

[NotNull]

Not yet; the SDK will be updated later on.

[nikov]

Thank you all for the helps.