Properties - GUI vs. ES.exe

[therube]

Properties - GUI vs. ES.exe

on a non-indexed Property
GUI can be relatively quick,
where ES.exe is apt to be relatively (or even) slow, always.

is that a caching issue, where the GUI does, & ES.exe does not?

c:/out audio: length:>3:00:00

vs.

ES.exe c:/out audio: !/100 length:">3:00:00"

if i then change the two to (& actually leaving the ES.exe as it was):

c:/out audio: length:>1:00:00

vs.

ES.exe c:/out audio: !/100 length:">3:00:00"

GUI is immediate (even though not indexed), where ES.exe takes just as long as before (even though its query was unchanged)

[void]

The GUI caches per window.

ES (and IPC3) caches per connection.



ES doesn't keep a connection open, once your results are returned, ES disconnects from Everything.

I will look into an Everything option to use only one query for IPC3.
-or-
Maybe make Everything IPC3 track the console window and use one query for each console window.

[void]

Looking at this a little more, it needs to be done ES side.

I need to implement an ES Server that exists while the console window is active.
After opening a console window and calling ES for the first time, the ES server is created.
The ES command is passed to the ES server and your results returned.
Multiple ES calls from the same console window will talk to the same ES server.
Once the console window is closed the ES server will exit.

I have put this on my TODO list for a future version of ES.

I will consider a quick fix option to use only one db connection in IPC3.
However, this db connection would never be released, so the cache might grow rather large, and there's not way to clear it without restarting Everything.