> What I would typically do is setup netem on an inbound qdisc and 
> whatever is under test on the outbound.
Thanks, this is good advice.

> even then, care is needed to ensure netem itself is not the bottleneck, 
> has an appropriate packet limit (I use millions), and that you are not 
> running out of cpu. For example it is really hard to pull 4gbit on cheap 
> hw with default qdiscs.
👍

As I'm not an expert regarding qdiscs, this command line example was 
useful showing how to configure an ingress qdisc:
https://serverfault.com/questions/984822/how-to-remove-the-ingress-delay-introduced-using-tc
(Note that it does not set a higher packet limit as you correctly 
recommended.)