Updating Database. How can I turn it OFF when starting EV?

[luckulucki]

Hello all

I'd like to ask,
if there is an option (which I did not found)to turn off the automatic updating of the database (and re-indexing all the lists+harddrives), while I start EV (or rebooting the Computer).

I've got an old Computer with veeeeeery slow drives and huge lists and just loading the EV DB would be fine, but updating it, takes about 3-5 hours, so EV is not usable AND makes the computer very slow too.
I have to kill EV via Task-Manager to work. Then I start EV when I quit working and -most of the time- the next morging, everything is ready to use.

Thank you all and be well!

P.S.
I'm using Version 1.4.1.969 (x64)

[vsub]

Well,just make it not start along with windows and run it manually
There is some options that you can disable to increase the loading but you will have to rebuild the database manually

But something may be wrong on your pc
I have been using everything before on Pentium 4 before with 1gb ram and it was working fast(normal 1tb hdd)
I also use it on a small laptop that was even weaker that that pc and again,no problems

Maybe you have too many options enabled in Indexes or\and USN Journal enabled
Can you post a screenshot of your Indexes settings

[luckulucki]

Hello and thank you for your time/help!

There is some options that you can disable to increase the loading but you will have to rebuild the database manually

What options exactly?

Can you post a screenshot of your Indexes settings

Sure thing. I would call my settings "minimal".

my index options

2020-05-04 20-58-06_Everything Options.png (36.88 KiB) Viewed 13565 times

Deactivating "Index recent changes" did not help, fyi.

Maybe you have too many options enabled in Indexes or\and USN Journal enabled

USN is enabled, yes.

my ntfs options

2020-05-04 21-06-25_Everything Options.png (6.4 KiB) Viewed 13565 times

Should I test disabling it? I read the help (some long time ago) and I considered the activating of USN as useful.
Also, as I wrote in my initial post, I don't want to turn off the "monitoring", but this:

2020-05-04 21-08-50_Everything.png (1.66 KiB) Viewed 13565 times

...but I guess, its the same thing. (The Statusline runs fast through the Re-Indexing processed of my filelists and also of my harddrives, but that "Updating database..." is still working since I wrote my initial post. In this time, I cannot use the EV search.

Btw: %TEMP% refers to C:\temp and it is a SSD (some years old though) and EV itself lives on another SSD drive.
All the indexed drives are SATA with sizez from 3TB to 10TB and worth some millions files. Maybe the filecount is a problem? Can I see how many files/folders are indexed?

Well,just make it not start along with windows and run it manually

Sure, that would help with not working with a laggy computer, but anyways, starting EV will take about 2-5 hours to complete the "Updating database" process.
So I can't use EV in that time, which I really want to.

Killing it (or just exiting it via right click) is ok for me.
When the Computer is turned on at 0600, but I work at 1000, everything is -most of the time- fine.

Thank you for your time!

[NotNull]

Take a look at this thread

[luckulucki]

Take a look at this thread

I Thank you very much!

-monitor-pause is currently sent to the active instance to pause the monitors, this will happen after the db has been loaded and updated.
I don't have an easy fix for this. I will address it in Everything 1.5.

Future versions of Everything (Everything 1.5+) will update in the background and you'll be able to search immediately after starting Everything.

So, atm, there is no help, but hope

I wish you all the best and thanks again for being so supportive!

[NotNull]

So, atm, there is no help, but hope

If you read further in that thread, you will see this:

Everything 1.4.1.967 fixes an issue with -monitor-pause not working as intended.


To start Everything with the monitors paused:
Everything -monitor-pause

To resume monitors:

• In Everything, type in the following search and press ENTER:
  /monitor_resume

I can confirm that this works as intended.

[luckulucki]

So, atm, there is no help, but hope

If you read further in that thread, you will see this:

Everything 1.4.1.967 fixes an issue with -monitor-pause not working as intended.


To start Everything with the monitors paused:
Everything -monitor-pause

To resume monitors:

• In Everything, type in the following search and press ENTER:
  /monitor_resume

I can confirm that this works as intended.

Hello,
I doubt this will solve the problem I described:

starting EV will take about 2-5 hours to complete the "Updating database" process.

Also, as I wrote in my initial post, I don't want to turn off the "monitoring", but this:

The Statusline runs fast through the Re-Indexing processed of my filelists and also of my harddrives, but that "Updating database..." is still working since I wrote my initial post. In this time, I cannot use the EV search.

[NotNull]

You wouldn't turn off monitoring permanent, but just when Everything starts.
As soon as you don't need Everything anymore, enter this in the search bar and press ENTER:

Code: Select all

/monitor_resume

That will re-enable monitoring and causing Everything to update it's index.
(Make it into a bookmark for easy access)

Next time you start Everything (with teh -monitor-pause option), Everything is available right away.
(but don't forget the /monitor_resume at the end of the day ..)

[luckulucki]

I understood, thank you, but that does not help as you both say.

The problem is not the monitoring, the problem is the Updating Database Process at the start of EV, which will be addressed in v1.5, if I read correctly.

So I'm starting EV via

Code: Select all

Everything.exe -monitor-pause

and this is what I get:

2020-05-09 23-26-59_I can type, but nothing is happening... no search is initiated, no nothing... th.png (30.86 KiB) Viewed 13533 times

I can't use (aka search for anything) EV until that Updating Database Process is finished. Unfortulnately, it takes hours, so EV practial unusable for this time.

[NotNull]

And you are running Everything 1.4.1.967 or later?

[luckulucki]

And you are running Everything 1.4.1.967 or later?

Ah, I forgot to add a screenshot in my last post, sorry. Yes, I do.

2020-05-09 23-49-08_Everything.png (17.74 KiB) Viewed 13531 times

[NotNull]

In that case: That seems like a bug to me.
First thought: file list related.

Try to start Everything with this command:

Code: Select all

everything.exe -monitor-pause -debug

In the debug window that also opens, you can follow what Everything is doing.

[luckulucki]

Here is the log.

Code: Select all

GetVolumePathNamesForVolumeName 234
GetVolumePathNamesForVolumeName W:
add found ntfs volume: \\?\Volume{CENSORED-W} | W: |  | 0000000002903af0
volume \\?\Volume{CENSORSHIP-E}: drive type 5
QueryDosDevice C: \Device\HarddiskVolume2
QueryDosDevice E: \Device\VeraCryptVolumeE
E:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-E}\ 3
E:\ is ntfs
QueryDosDevice H: \Device\HarddiskVolume7
QueryDosDevice O: \Device\VeraCryptVolumeO
O:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-O}\ 3
O:\ is ntfs
QueryDosDevice P: \Device\VeraCryptVolumeP
P:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-P}\ 3
P:\ is ntfs
QueryDosDevice W: \Device\VeraCryptVolumeW
W:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-W}\ 3
W:\ is ntfs
volume: \\?\Volume{CENSORED-C} | C: |  found 1
volume: \\?\Volume{CENSORED-E} | E: |  found 1
volume: \\?\Volume{CENSORED-H} | H: |  found 1
volume: \\?\Volume{CENSORED-O} | O: |  found 1
volume: \\?\Volume{CENSORED-P} | P: |  found 1
volume: \\?\Volume{CENSORED-W} | W: |  found 1
ntfs volume create list 0.027464 seconds
E:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-E}\
E:\ is refs
O:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-O}\
O:\ is refs
P:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-P}\
P:\ is refs
W:\ GetVolumeNameForVolumeMountPoint \\?\Volume{CENSORED-W}\
W:\ is refs
new thread (0)
Loading structure 00002021: 3022012 folders, 9155007 files...
_db_index_add 0: 0, 000000000034dd90
bind to family 23, protocol 6, socktype 1
_db_index_add 1: 0, 000000000034de00
bind to family 2, protocol 6, socktype 1
_db_index_add 2: 0, 000000000034de70
_db_index_add 3: 0, 000000000034dee0
HTTP server online.
_db_index_add 4: 0, 00000000028d9290
_db_index_add 5: 0, 00000000028d9300
_db_index_add 6: 1, 0000000002903c30
_db_index_add 7: 1, 0000000002903c80
_db_index_add 8: 1, 0000000002903cd0
_db_index_add 9: 1, 0000000002903d20
_db_index_add 10: 1, 0000000002903d70
_db_index_add 11: 1, 0000000002903dc0
_db_index_add 12: 1, 0000000002903e10
_db_index_add 13: 1, 0000000002903e60
_db_index_add 14: 1, 0000000002903eb0
_db_index_add 15: 1, 0000000002903f00
_db_index_add 16: 1, 0000000002903f50
_db_index_add 17: 1, 0000000002903fa0
_db_index_add 18: 1, 0000000002903ff0
_db_index_add 19: 1, 0000000002904040
_db_index_add 20: 1, 0000000002904090
_db_index_add 21: 1, 00000000029040e0
_db_index_add 22: 1, 0000000002904130
_db_index_add 23: 1, 0000000002904180
_db_index_add 24: 1, 00000000029041d0
_db_index_add 25: 1, 0000000002904220
_db_index_add 26: 1, 0000000002904270
_db_index_add 27: 1, 00000000029042c0
16 29
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000000000, current focus 0000000000000000
cached oneclickactivate 0
enter setfocus
leave setfocus
enter main loop
new results 0
convert all folder parent indexes into folder parent folders 0.095872 seconds
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 000000000229053c, current focus 000000000229053c
find recent changes on C:
open volume \\?\Volume{CENSORED-C}
opened 644 0.005206
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 000000000229053c, current focus 0000000000000000
new results 0
new results 0
new results 0
new results 0
no search history hwnd
new results 0
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 000000000229053c, current focus 000000000229053c
find recent changes on E:
open volume \\?\Volume{CENSORED-E}
opened 644 0.003534
cl:
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 000000000229053c, current focus 0000000000000000
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 000000000229053c, current focus 000000000229053c
cl:
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 000000000229053c, current focus 0000000000000000
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 000000000229053c, current focus 000000000229053c
cl:
WM_ACTIVATE 0000000000000001 00000000019716a4, lastfocus 000000000229053c, current focus 00000000019716a4
SetForegroundWindow failed 00000000
SetForegroundWindow2 failed 00000000
shutdown
destroy ui
HTTP server offline.
DB_WAIT: db_save waiting...

I started EV as told,
waited a few secs, typed in a search (that was somewhat around the time the message "no search history hwnd" came up, my searchterm was "test"), waited, waited,
after some minutes, I quitted EV, because the computer is unusable, when EV is updating its DB.

[luckulucki]

Hi,

here is another log.

I started EV and waited about 20 minutes, but the updating process did not stop.
I typed in "test" as a searchterm and nothing happened, as described in the above post.

Then I went to bed and this morning the updating process was finished.

Unfortunately, the log shows no date, so we can't actually see, how long that updatig database process took, but from my experience, it took at least 4-5 hours.

Hope this helps

(btw. at about 4 o'clock, some filelists are updated by the server, so that might also be reflected in the log)

Code: Select all

[...]
check for file list changes
checked for file list changes in 0.000872 seconds
search 'test' filter '' sort 2
term 000000000038d720, flags: 2144, next: 0000000000000000, notnext: 0000000000000000
folderop: 10, fileop: 10, term: test
SET SORT 2
found 6109 folders, size 65640, db search time taken: 0.796557 seconds
found 117198 files, size 984888, db search time taken: 2.678596 seconds
total size 422129759992, calculated in 0.004195 seconds
set sort 2 1
already sorted
finished sort, time taken 0.000248 seconds
update selection 0.000001 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000176 seconds
new results 123307
selection: 1/1: \\Server\Dir\Folder\M\Verz]
exec: first expr
exec: command $exec("%1")
exec: fullfilename \\Server\Dir\Folder\M\Verz]
exec: depth 0
exec: exec "%1")
exec: depth 1
exec: got "\\Server\Dir\Folder\M\Verz]"
exec: shellexecute (idlist) file:\\Server\Dir\Folder\M\Verz] param:
WM_ACTIVATE 0000000000000000 0000000000162464, lastfocus 0000000000a010b2, current focus 0000000000a010b2
Enter ShellExecuteExW
\\Server\Dir\Folder\M\Verz
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 11 000000000000002d 0000000000000000
when ready 8 0000000000000000 0000000000000000
Leave ShellExecuteExW
sub buf killed
set 1 run history in 0.078496 seconds
exec: main thread regained focus
new results 123307

May I propose to add some sort of DATE in the log file? ATM there is no way of telling when something is happening and how long it really takes.

[NotNull]

May I propose to add some sort of DATE in the log file? ATM there is no way of telling when something is happening and how long it really takes.

If you start Everything like this, it will create a logfile with timestamps in %TEMP%. :

Code: Select all

Everything.exe -debug-log -debug 

Everything Debug Log.txt

Code: Select all

2020-05-12 00:53:38.009: Everything
2020-05-12 00:53:38.040: Version 1.4.1.976 (x64)
2020-05-12 00:53:38.056: Windows NT 6.2
2020-05-12 00:53:38.071: Processors 2
2020-05-12 00:53:38.103: IsAdmin 0
2020-05-12 00:53:38.134: AppData 0
2020-05-12 00:53:38.149: Service 2
2020-05-12 00:53:38.165: cmdline Everything.exe  -debug-log -debug
2020-05-12 00:53:38.181: load localization
2020-05-12 00:53:38.212: lng file opened!
2020-05-12 00:53:38.243: header size 770
2020-05-12 00:53:38.274: version 1
2020-05-12 00:53:38.306: got header
2020-05-12 00:53:38.321: system default lid 0409
2020-05-12 00:53:38.337: count 33
2020-05-12 00:53:38.743: ole initialize: 00000000
2020-05-12 00:53:38.759: create mutex

....

[luckulucki]

Ok, thanks,

was the log output useful in any way for you?

Should I do something else to help?

Otherwise, I just continue and wait until 1.5 comes out

btw:
does the /monitor-resume gives any output ?
When I enter it into the search field, I see a shorty quering and thats it.
I would expect, EV starts updating the database or something else which indicates, its "working" again, but nothing at all...

first this

q.png (10.43 KiB) Viewed 13497 times

than that

r.png (14.52 KiB) Viewed 13497 times

than nothing more...

[NotNull]

You should use /monitor_resume instead of /monitor-resume.

The only one who knows what all these entrie sin the debug log mean, is void (the author of Everything). Can't help you there. Sorry.

[luckulucki]

You should use /monitor_resume instead of /monitor-resume.

Ok, that was dumb copying from one of the above posts, w/o initializing the $brain variable before.... thanks for pointing out!

The only one who knows what all these entrie sin the debug log mean, is void (the author of Everything). Can't help you there. Sorry.

Ok.
For the case, that he maybe reads this,
I add this from the Everything Debug Log.txt, because I have a lot of those lines, worth about ~1GB in size of entries from a ~2GB logfile

Code: Select all

2020-05-13 13:03:19.581: USN 2020-05-13 13:03:19.582: DATA_TRUNCATION 2020-05-13 13:03:19.582: store.bin
2020-05-13 13:03:19.582: USN 2020-05-13 13:03:19.583: DATA_EXTEND 2020-05-13 13:03:19.583: DATA_TRUNCATION 2020-05-13 13:03:19.583: store.bin
2020-05-13 13:03:19.584: USN 2020-05-13 13:03:19.584: DATA_EXTEND 2020-05-13 13:03:19.584: DATA_TRUNCATION 2020-05-13 13:03:19.584: CLOSE 2020-05-13 13:03:19.585: store.bin
2020-05-13 13:03:19.585: USN 2020-05-13 13:03:19.586: DATA_TRUNCATION 2020-05-13 13:03:19.586: store.bin
2020-05-13 13:03:19.586: USN 2020-05-13 13:03:19.586: DATA_EXTEND 2020-05-13 13:03:19.587: DATA_TRUNCATION 2020-05-13 13:03:19.587: store.bin
2020-05-13 13:03:19.587: USN 2020-05-13 13:03:19.588: DATA_EXTEND 2020-05-13 13:03:19.588: DATA_TRUNCATION 2020-05-13 13:03:19.588: CLOSE 2020-05-13 13:03:19.588: store.bin
2020-05-13 13:03:19.589: USN 2020-05-13 13:03:19.589: DATA_TRUNCATION 2020-05-13 13:03:19.589: store.bin
2020-05-13 13:03:19.590: USN 2020-05-13 13:03:19.590: DATA_EXTEND 2020-05-13 13:03:19.590: DATA_TRUNCATION 2020-05-13 13:03:19.591: store.bin
2020-05-13 13:03:19.591: USN 2020-05-13 13:03:19.591: DATA_EXTEND 2020-05-13 13:03:19.591: DATA_TRUNCATION 2020-05-13 13:03:19.592: CLOSE 2020-05-13 13:03:19.592: store.bin
2020-05-13 13:03:19.592: USN 2020-05-13 13:03:19.593: DATA_TRUNCATION 2020-05-13 13:03:19.593: store.bin
20

Maybe that file causes the trouble on my system... It might be that file C:\Users\user\AppData\Local\Dropbox\metrics\store.bin

I will now check how to ignore special files with everything.

Thanks for your help and time!

I'll just wait excited for the 1.5

Enjoy your time!