I waffle back and forth all the time.
I have 300M up and down from FiOS and honestly it’s pretty good out of the box, but it isn’t perfect all the time.
I’ll go a month with FastTrack on and nothing but the default only-hardware-queue set, but then we’ll get a zoom or YouTubeTV hiccup and I’ll convince myself that queueing will help. So then I’ll throw cake or fq_codel on a simple queue on eth1, but then I’ll convince myself that it isn’t doing anything, as there will be the same random hiccup. Then I’ll mistrust the simple queue and throw a cake or fq_codel queue tree on eth1 and the bridge so that FastTrack can stay on, but then I’ll wonder if that’s unnecessarily slowing down the bridge due to it needing to be set with a max-limit of 290ish, so I’ll just take it all off and start over with nothing. I also tried just changing the queue type to fq_codel for all the interfaces, but I couldn’t figure out if it was doing anything without having any max-limits set.
At the moment I just have an fq_codel queue tree on eth1 at max-limit 290M to smooth anything coming from my network, but I’m leaving the bridge/download with just hardware-only-queue.