Everything freezes upon multiple zipfilenames search

[anmac1789]

Hello, when I multiple (about 30+ or more) "filename"|zipfilenames:"filename.ext" combinations in the search bar, everything slows down and lags. Every few minutes, everything freezes and then unfreezes and the scroll bar lags alot every few seconds or minutes. Why is this happening ?

[NotNull]

Everything will have to open every zip-file to see if it contains "filename.ext".
You might have included "slow folders" in your query (cloud storage? network?) which causes this to take some time.
Did you see the progress bar in the statusbar all this time?

On the other hand, I tried the following search on my (mediocre) system and that took about a second (400+ zipfiles to search through)
No lagging whatsoever..

Code: Select all

c:   ext:zip   zipfilenames:"filename.ext"

[anmac1789]

Everything will have to open every zip-file to see if it contains "filename.ext".
You might have included "slow folders" in your query (cloud storage? network?) which causes this to take some time.
Did you see the progress bar in the statusbar all this time?

On the other hand, I tried the following search on my (mediocre) system and that took about a second (400+ zipfiles to search through)
No lagging whatsoever..

Code: Select all

c:   ext:zip   zipfilenames:"filename.ext"

nope, the paths are all from local folders in C:\ and I did see the progress bar and I waited until everything was finished loading. How come your system processed 400 zip files so fast?

[NotNull]

No idea. I just rebooted to exclude caching from the equation; still less than 2 seconds.

( FWIW: 400+ zipfiles = 2,1 GB )

[anmac1789]

No idea. I just rebooted to exclude caching from the equation; still less than 2 seconds.

( FWIW: 400+ zipfiles = 2,1 GB )

I'm searching across multiple ssd's, hdd's and some zip files are rather large 20-30 GB+

[void]

Please try including the following in your search:

content-max-threads:1

Does this help with the freezing?

[anmac1789]

content-max-threads:1

What does this do exactly ?

[void]

Limit Everything to gather property values with a single thread only.

By default Everything will use a thread on each logical CPU to read content from SSDs.

[anmac1789]

Limit Everything to gather property values with a single thread only.

By default Everything will use a thread on each logical CPU to read content from SSDs.

interesting but really though it made 0 difference

[void]

A mini crash dump will help find the issue.

Could you please send a mini crash dump when Everything freezes:

• Download Process Explorer from Microsoft:
  https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
• In Process Explorer, select Everything64.exe (If there is two, select the one using the most memory)
  ---wait for Everything to freeze---
• Right click Everything64.exe and under Create Dump, select Create Mini Dump.
• Choose a filename and click Save.
• Please send this file to support@voidtools.com

[therube]

multiple (about 30+ or more) "filename"|zipfilenames:"filename.ext" combinations

What version of Everything?

So this "30", is that 30 "OR" pairs:
"filename1"|zipfilenames:"filename.ext" | "filename2"|zipfilenames:"filename.ext" | ... "filename30"|zipfilenames:"filename.ext"

or more like what NotNull posted?
(I suppose the above is not correct as it would actually require brackets...)

[anmac1789]

multiple (about 30+ or more) "filename"|zipfilenames:"filename.ext" combinations

What version of Everything?

So this "30", is that 30 "OR" pairs:
"filename1"|zipfilenames:"filename.ext" | "filename2"|zipfilenames:"filename.ext" | ... "filename30"|zipfilenames:"filename.ext"

or more like what NotNull posted?
(I suppose the above is not correct as it would actually require brackets...)

There are 30 pair's for example "filename.jpg"|zipfilenames:"filename" x 30 seperated by a | "OR" pairs

[therube]

And you're using 1352a ?

The OR's are "expensive" compared to the method that NotNull shows (if you're able to use something like that).

[NotNull]

The following likely won't solve your issue (mini dump or debug log are needed for that), but consider rearranging your search query.

Everything will probably rearrange and optimize the query itself (did not check) and caching will help too, but the current query opens all zipfiles to find file1 and when done, opens all zipfiles to find file2 and when done ... (you get the point )
So searching for 30 filenames will open each zipfile 30 times ..


The following opens each zipfile once and searches for all mentioned files, closes the zip and opens the next zip file (... etc)

At the very least, the following query is much easier to type out (copy/paste the ; delimited list filenames ):

Code: Select all

filelist:filename1.jpg;filename2.bmp;filename3.tif;"name with space.txt"  |  zipfilenames:ilename1.jpg;filename2.bmp;filename3.tif"name with space.txt"

[anmac1789]

And you're using 1352a ?

The OR's are "expensive" compared to the method that NotNull shows (if you're able to use something like that).

yes I'm using the latest alpha version 1352a

I think this code needs some adjustments:

Code: Select all

filelist:filename1.jpg;filename2.bmp;filename3.tif;"name with space.txt"  |  zipfilenames:ilename1.jpg;filename2.bmp;filename3.tif"name with space.txt"

to something like:

Code: Select all

filelist:filename1.jpg;filename2.bmp;filename3.tif;"name with space.txt"  |  zipfilenames:filename1.jpg;filename2.bmp;filename3.tif;"name with space.txt"

What is the point of having a filename list instead of just a quoted filename.extension ?

[NotNull]

I think this code needs some adjustments:

You are right! (should have mentioned that it was untested, although that still would not have prevented these typos)

What is the point of having a filename list instead of just a quoted filename.extension ?

Instead of an OR'ed list of filenames? The only reason is re-usability; you can copy file1;file2;file3 to be reused for the zipfilenames: part.
(I'm lazy ..)

EDIT: ... and easily convert it into a Filter later on if needed.

[anmac1789]

I think this code needs some adjustments:

You are right! (should have mentioned that it was untested, although that still would not have prevented these typos)

What is the point of having a filename list instead of just a quoted filename.extension ?

Instead of an OR'ed list of filenames? The only reason is re-usability; you can copy file1;file2;file3 to be reused for the zipfilenames: part.
(I'm lazy ..)

EDIT: ... and easily convert it into a Filter later on if needed.

My search terms constantly change with filenames and zipfilenames since im searching for thousands upon thousands of files

[NotNull]

Not sure what you want to say.
Do you mean that this is easier with an OR'ed list of filenames instead of a semi-colon delimited list of files?

[void]

What is the point of having a filename list instead of just a quoted filename.extension ?

filelist: is faster than filename1.ext|filename2.ext|filename3.ext|...

filelist: will:
Create a sorted list of filenames.
Match the whole filename using a binary search.

[anmac1789]

What is the point of having a filename list instead of just a quoted filename.extension ?

filelist: is faster than filename1.ext|filename2.ext|filename3.ext|...

filelist: will:
Create a sorted list of filenames.
Match the whole filename using a binary search.

is filelist going to find all the filenames in all the paths that exist anywhere in the C drive? similarly how filename.jpg finds all filenames weather its case sensitive or not..What if I want to disable matchwhole filename using filelist and folderlist ?

[void]

is filelist going to find all the filenames in all the paths that exist anywhere in the C drive?

Yes.

The different between:
filelist:filename.jpg and filename.jpg is filelist: will match the whole filename.
filename.jpg on its own will do a partial filename search. (for example it will match "new filename.jpg")

Neither search is case sensitive.
You can use the case: modifier on both searches to match case.



filelist: can do partial filename searches by including wildcards.
For example:
filelist:*filename*.jpg