It's hard to generalize. Personally, I actually HAVE disabled both on my network facing system. I have enough protection (and discipline) in my environment here that malware never even gets close, and I especially have several layers of security blanket that keep my browsers and applications from visiting known bad sites online. Not to mention I turn that stupid UAC off (making a security Meltdown kind of a moot point). I guard the borders better and don't worry as much about policing microsecond by microsecond operation, which sounds like it may be your philosophy too.
But everyone's needs are different. Would I suggest disabling the mitigations for the general public, especially those who are not technically savvy? Probably not.
My point here is that even when disabled there's a significant performance penalty. I guess this must be because besides the memory manager reload operations that were added (and which can be disabled) the kernel and system software in Windows have been recompiled with changes to do certain operations a different, less efficient way to avoid meltdown concerns. I'm always looking for more detail on this, and I appreciate the discussion.
The surprising part is that hardly anyone's talking about this! I guess it must be a combination of folks in general doing things that are not easily measurable and their systems already being burdened-up with a bunch of performance-sapping software, so what's one more little slowdown?
-Noel