CXPACKET bottleneck.

It does not look terrible, do the users complain about performance?
https://www.brentozar.com/archive/2013/08/what-is-the-cxpacket-wait-type-and-how-do-you-reduce-it/

A good read as below:
knee-jerk-wait-statistics-cxpacket

Please mark this reply as answer if it solved your issue or vote as helpful if it helped.
Blog
LinkedIn

Hi,

CXCONSUMER waits are generally benign, encountered as a normal part of parallel(CXPACKET) execution. By making the consumer threads register benign CXCONSUMER waits, the remaining CXPACKET waits from the producer threads are what indicate a performance problem.

Also check this similar case:
https://dba.stackexchange.com/questions/210795/what-can-i-do-about-high-cxpacket-waits

My starting question is are you facing performance issue with these waits, the whole answer depends on that. As others have mentioned these are mostly benign waits and in case of issue they are not actually the issue but the next most wait coming is what causing it. In your case if you tell me this is a problem then I would ask you to look at SOS_SCHEDULER_YIELD waits. May be the max degree of parallelism is not set correctly, may be their is CPU pressure. We need to dig deeper and check. The CXCONSUMER in this case can be ignored.

Thanks all for the answers!

A lot to read and learn, thanks. Well, I can't say that we are having performance problems, but I like to optimize our production database, as always. Follow our settings:

I am thinking of configuring MAXDOP to 8, according to Microsoft’s recommendations in KB 2806535. But how can I better measure if there is a CPU pressure?

It doesn't end here. Let's talk more.