mastercoms-high improves responsiveness with better preemption and execution of tasks. It helps even with just background processes.
That's what priority is, yeah. But Windows should handle background process management enough that this shouldn't be an issue, no? And if you're seeing real benefit from this you should probably be using something like CPUCores (or one of its non retarded variants) that isolates background processes to separate cores.
mastercomsIt saves a bit of memory and decreases startup time by the joystick system from starting. It still works, you can check this by comparing the stdout output from TF2 when -nojoy is present and removed.
Okay, so the documentation that it was removed in the orange box engine is wrong - but how much memory/startup time does it really save?
mastercomsNo, this tells TF2 how many worker threads are available for tasks. TF2's automatic detection for worker thread count is limited to 3 threads, so -threads allows you to force a higher count.
I thought it's been documented that any threads over 3 that it creates anyway are essentially zombie processes? Wouldn't mind a correction on that.
mastercomsBut some people have problems with raw input, so it is still useful for those with raw input disabled.
I'm willing to bet he has m_rawinput 1 in his autoexec, in which case that launch argument is pointless.
Just like the majority of these commands, they aren't ALL useless, but their use cases are so far and few between that it's probably a good idea to not propagate them on the internet.