Run History, what constitutes a "run"

If you are experiencing problems with "Everything", post here for assistance.
therube
Posts: 5869
Joined: Thu Sep 03, 2009 6:48 pm

Run History, what constitutes a "run"

Post by therube »

Run History, what constitutes a "run" ?

As in (on 1 particular computer), Run History.csv contains 109K entries.
Of that 57K entries are .jpg/.png.
36K entries are .mp4/.mkv/.jpg (so the .jpg are dup'd in the 57K above).

The 36K entries are "bogus" files. Simply files created for various testing purposes, the majority of which are 0-bytes, & at most < 1000-bytes, & none are indicative of what they are based upon their named file extensions.


So, there is no way that these files were in any fashion "run" (by me).
Though given the file types, they might have been (or attempted to have been) "indexed", like to pull a "thumbnail/icon" (or whatnot) by Windows itself.

Does (or perhaps some time in the past, did) Everything consider such (what I'll call, 'Windows runs') as "runs", so they ended up in Run History.csv?


On a different computer, Run History.csv looked like:
  • 67 .m4a
    611 .jpg
    929 .mp3
    368737 - all else, so (guessing) mostly video:
(360K is a rather huge number, no.)



Kind of wonder if I shouldn't disable run_history.csv?
Or maybe (manually) set Run History to only specific programs that I might want to "find" that way.
On the system that I am on now, there is literally 1 item in Run History that is of significance.

Can I set that 1, remove all else, & set the file to read-only (after having closed Everything, first)?
Would that cause any issues?
(Actually I probably would not do that, but knowing that I could, that it would be OK...)
void
Developer
Posts: 20417
Joined: Fri Oct 16, 2009 11:31 pm

Re: Run History, what constitutes a "run"

Post by void »

As in (on 1 particular computer), Run History.csv contains 109K entries.
That's a lot of run history.
It will take Everything about 1 second to load 100,000 run history items.
Everything uses about 10MB per 100,000 run history items.

To check the performance:
Type in the following search and press ENTER:
/restart-debug-log

Everything will restart with debug logging enabled.
In Everything, from the Tools menu, under the Debug submenu, click Stop debug logging.
This will open your %TEMP%\Everything Debug Log.txt
Look for the following lines:
loaded run history in <x> seconds
run history data count: <run history item count>, data: <run history size> bytes



So, there is no way that these files were in any fashion "run" (by me).
If you can filter these files, eg:
"c:\path\to\files\I\do\not\run\" run-count:<10

Then from the File menu, click Set Run Count...
Set the run count to: 0
This will delete the run history for these items.


Does (or perhaps some time in the past, did) Everything consider such (what I'll call, 'Windows runs') as "runs", so they ended up in Run History.csv?
No, Run history is limited to items run from Everything.


(360K is a rather huge number, no.)
It is a lot.
Everything is pretty efficient with run history, this is only going to be about 30MB of RAM and 3 seconds to load.


Kind of wonder if I shouldn't disable run_history.csv?
Disable it if you don't sort by run count, or don't use ENTER from the search box to select the most run item.
Disabling run history doesn't delete your run history, so you can safely toggle it.
Tools -> Options -> History -> Uncheck Enable run history.


Or maybe (manually) set Run History to only specific programs that I might want to "find" that way.
There's currently no option to filter which items are allowed to have run history.
I'll consider a filter, I can see only allowing *.exe as being useful.
For now, you would occasionally have to trim your history by searching for !*.exe and setting the run count to 0.


Can I set that 1, remove all else, & set the file to read-only (after having closed Everything, first)?
Yes.
Make a backup of your Run History.csv first.
Select everything expect that one file.
From the main File menu, click Set Run Count.
Set the run count to 0
Exit Everything and set your Run History.csv to read-only.



Consider enabling Keep run history for 90 days:
  • In Everything, from the Tools menu, click Options.
  • Click the History tab on the left.
  • Check Keep run history for 90 days.
  • Click OK.
Everything will now automatically delete stale run history.


Would that cause any issues?
No.
therube
Posts: 5869
Joined: Thu Sep 03, 2009 6:48 pm

Re: Run History, what constitutes a "run"

Post by therube »

C:\DEV\LOCATE\runhist>wc -l run*
109235 Run History.csv

2026-10-30 14:30:05.737: loaded run history in 1.008994 seconds
2026-10-30 14:30:05.737: run history data count: 109234, data: 11986029 bytes
2026-10-30 14:30:05.737: run history ptr count: 104762
2026-10-30 14:30:05.737: total run history memory usage: 14281881 bytes