39 ms·
Now that there are nice tools like Process Explorer, it's less of an issue. Back in the day, you'd pull your hair out. Even so, the original premise of perform
by mysterydip 9y ago
Now that there are nice tools like Process Explorer, it's less of an issue. Back in the day, you'd pull your hair out.
Even so, the original premise of performance doesn't hold water to me. I load a process that has 10 services inside so I can use two of them, and that's somehow reduced memory compared to just running the two, just in case I want to run the other 8 later? Some of those services I have disabled and never want to run. It's still taking up the memory.
- ethbro 9y agoStill, if MS is going to do it, then the onus seems to be on them to surface it in built-in tools.