It seems like there's a potential for a lot of workload imbalance here where one of the Frame-buffer units has emptied its Rasterizer 0 queue, but is waiting on the other Frame-buffer unit to do the same.
It seems like there's a potential for a lot of workload imbalance here where one of the Frame-buffer units has emptied its Rasterizer 0 queue, but is waiting on the other Frame-buffer unit to do the same.