A bit of background to my question:
I've found it very difficult to search for an exact answer to this question, and an exact answer is the only thing I'm looking for, if that answer exists. I'm on Windows 10. I'm a developer and a power user, I have multiple IDE's open, multiple VMs, about 200+ chrome tabs spread over multiple chrome instances and multiple monitors, etc, and multiple programs running. I don't wish for my workflow to be critiqued, since this is how I enable myself to be maximally productive. If there's other ways, I'm sure we could save that for a philosophical discussion some other time.
With that disclaimer out of the way, I'd like to ask my question, which seems simple but I can't find the answer to it: How do I find out when RAM is a bottleneck to instant "alt-tab" access between open processes?
For example, from my research of windows virtual memory I understand Windows will cache frequently used programs etc. I don't care about this feature since every program I need to use, I want instant access to it (no delay) and thus it is already open.
I notice however that when alt-tabbing between program instances that are already open, especially an open program that I haven't had in-focus for quite some time, there will be a 2-5 second delay in regaining access to that program. That is unacceptable for how I like to operate.
I would like to specify this: Installing additional physical RAM is not a problem for me. That's what I want to do to overcome this, not make any other compromise whatsoever such as running less programs.
The only question I have is how do I quantitatively determine, through the Task Manager or elsewhere, when RAM is a bottleneck to my current usage demands, other than just observing the 2-5 second delay when alt-tabbing between some programs? What metric in the Task Manager, Resource Monitor, or elsewhere can I use to see when Windows has "hit its limit and needs to start caching, compressing, paging" or doing whatever else it has to do to compromise "instant alt-tab snap access" to an already open process?
Looking at memory in Task Manager, it is as follows:
Obviously "Available" is not the correct metric to answer my question, since there is still a slight delay when alt-tabbing between applications that haven't been active a long time (but nevertheless are still open, and haven't been closed since that time).
What metric can I use? Is it the fact that (Compressed) is above 0? Does any compression mean that my RAM is now a bottleneck to instant alt-tabing? Or would compression still take place if it wasn't? Or is it Cached that's the indicator? Or is it Committed?
What is the indicator that adding more RAM would be useful other than the argument "more RAM is always useful"? I'd like to see for myself that RAM is a bottleneck in some way via a metric before deciding to add more RAM. I want to know which metric that is, and also the assurance that adding enough RAM (some eventual amount) for my current open-process demands would eliminate any delay when alt-tabbing, or whether this is unavoidable as it's a design flaw of Windows 10 that can't be avoided no matter how much RAM there is? I'm assuming this isn't the case, but if it is, I'd like to know that too.