In one of the servers it always shows a steady full bar of Memory/CPU waits. But when I use some of the dmv queries, it doesn’t match. Any ideas?
When you see memory/cpu, that's actually an absence of waits. It means that the query is executing and likely the most significant activity is doing logical reads (cpu fetching data from cache). The reason we track it is that from an end user perspective, wall clock time is still passing, so even though that's an efficient activity, there is still impact.
Look at cpu metrics and make sure nothing is under pressure (maxed out). If not, in any context, the vast majority of time in memory/cpu is a good profile and should be desired.
