It seems implementation is buggy when e.g. using local ETP:
- Everything.exe -connect "localhost:10021" -drive-links
Search window is opened immediately with data loaded via local ETP
No CPU or memory spikes generated. Memory usage of service proccess is about 80 MB and 20 MB for "user process"
- Everything.exe -connect "localhost:10021" -drive-links -minimized
Search window is minimized and another icon in the tray.
When opened via minimized icon, Search window is opened immediately but no data visible as it is in state "Sending query..." for another 45 seconds.
1 core is fully loaded by Everything process running as a client service, memory raised 4x (300 MB). Everything "user process" generates another 15% CPU load on quad core, memory raised above 200MB. Memory footprint was linearily moved from service process to user process so in the end service process dropped to 80 MB and user process raised to about 220MB
Then data were loaded via local ETP.
When clicked on tray icon, data are presented immediately.
- Everything.exe -connect "localhost:10021" -drive-links -startup
Everything icon is started in tray only.
When opened, [local database file] was initiated and loaded so ETP server params were totally ignored.
Thank you for finding the bug and thanks for your work on this great piece of SW
When many users are logged on the system (terminal server), each user starts own Everything process with its unique local DB. In such cases memory and CPU footprint is much bigger than running only one "client service" indexing to the local "master DB" and users are connecting there via ETP. In such case each user takes 10-20 MB memory max instead of minimum 80 MB each in the previous case.
If there is any other option how to run single instance on terminal server, with one master DB, please let me know