[Solved] Hopes of minimum working set as of 1.5.0.1411b

[Herkules97]

I moved my Monolith instance to v1.5.0.1411b from v1.5.0.1390a. With this change I also made the shortcut relative and decided to finally try out min_working_set_size.
The instance is 25-27GB, I don't have bytes from Process Explorer so Idk and cba to check elsewhere.
I set the minimum size to 20GB, not the GiB kind. 20,000,000,000.
At first it seemed fine, it went down to 21GB in Process Explorer instead of going all the way to the usual 2GB or whatever it is.
Now it's been at 6.7GB for several minutes.

This isn't much of an issue, but previously I used pagefile on my M.2 SSD and that seems to have broken or the connector on the Mobo has. Either way I am not going to use it for pagefile anymore in case it breaks more even if an external enclosure can still read from it.

So now that I run pagefile from the OS device I only get about 150MB/s when it is mostly occupied fully. As in reading from pagefile to Monolith has occupied 89% of supposed read total for the device according to Task Manager.
This takes however long it takes when making a search from Monolith being almost entirely in sleep state at around 2GB.

I figured if I did use working set minimum, I could prevent it doing this. Now 8 minutes later it's at 6GB WS from 6.7GB. Will probably go down further as time goes on.
I have to keep watch on my RAM usage anyway when doing heavier tasks, so I am not unaware if it starts reaching limits.

How do I force it to keep Monolith in a woken(?) physical-usage state? Virtual_lock? Clearly minimum WS does not work.
It says it needs both max and min in use..Is virtual_lock meant to be what ensures it? If so how do I know what to put? If say Monolith needs to rebuild and I only put 35GB max and it needs 48GB at its peak? Do I put a generous amount like 60GB to ensure it doesn't fail? And maybe 23-24GB minimum so it's only around 1-3GB away from private bytes max? 15 total minutes later Monolith is now at 2.8GB WS.

[void]

Set virtual_lock, min_working_set_size and max_working_set_size.

Set min_working_set_size to the minimum size to keep in physical RAM, eg: 20GB (20,000,000,000)
Set max_working_set_size to the maximum size to keep in physical RAM, eg: 48GB (48,000,000,000)
Set max_working_set_size well above your typical memory usage.
If Everything allocates more memory than max_working_set_size, things will get paged to disk.
If you have plenty of ram, use 60GB.
Just don't set max_working_set_size to your total RAM size. Try to leave at least 16GB available for the OS and other apps.

[Herkules97]

Set min_working_set_size to the minimum size to keep in physical RAM, eg: 20GB (20,000,000,000)

When EBV rebuilds, it usually goes down in physical usage, it's fine to have say 23GB minimum still? I've put it at that, just curious what would happen if it needs to rebuild as its RAM usage can fluctuate from say 11GB to 50GB during that.
It'll work as normal? It will crash?

[void]

It will work as normal, just start paging to disk when you go over max_working_set_size.

[Herkules97]

It will work as normal, just start paging to disk when you go over max_working_set_size.

I recently used Monolith and..It's not sticking. Working Set was around 2.7GB and went up to 6.3GB as expected for the search I did.
The settings are..
min_working_set_size=23000000000
max_working_set_size=60000000000
virtual_lock=1
Is it just that it doesn't use pagefile but it still has to "awaken" but it's at the speed of the RAM sticks up to 23GB?
I figured it meant that it was always at 23GB working set or tried to be there.

[void]

Did you restart Everything after changing virtual_lock, min_working_set_size or max_working_set_size?

I figured it meant that it was always at 23GB working set or tried to be there.

This is what should be happening.

[Herkules97]

Did you restart Everything after changing

I see, I will restart then.
No, I may have forgotten
If I don't reply again, it means restarting worked.