Ah! That makes sense then.

Yeah, learning how to deliberately overload the data cache vs the plan cache vs crushing the O/S space, etc., are all useful things. Good idea. Gives you a better idea of what can do those kinds of things, so you can fix it when it happens in the wild.

Try some things like loading too many big tables into active queries, all at the same time.

Try firing off a bunch of hyper-complex queries all at once.

Try non-deadlock long locks.