General • Re: Filled up RAM breaks usage of Everything

But if my current system has 64 GB of RAM and my next one will probably have 128 GB then, then should not I set min_working_set_size to 3 GB and max_working_set_size to 6 GB in order to make sure Everything will run smoothly, especially when I reconnect my huge archive drives?

I as already said, I pre-cache - quite a few properties of multimedia files. Like for example amount of channels or presence of subtitles; and I have hundred of thousands of such files on my system, plus millions on offline archives. Smooth handling of them on a daily basis is a priority for me

And I know you said

Set min_working_set_size and max_working_set_size to a little more than your normal Everything RAM usage.
[...]

But what constitutes as normal usage? When Everything is idle because nothing new is being indexed or searched for?

And should not the MAX value be significantly bigger than MIN? I mean: whats the point of having them at a similar or even the same level?


All in all: if I do not want my workflow to suffer from slowing of Everything during data transfers to my archive drive and them becoming a subject of newly added Properties to my indexing array, the I should anticipate increased demand for RAM by Everything in future - and thus grand it those GBs ahead of time, right?

Statistics: Posted by Thy Grand Voidinesss — Fri Aug 22, 2025 7:23 am

---