From the review of the screenshots, we can see that the Pending Delete Records fluctuate quite a bit, with a large amount of Pending Deletes in late May.
The overall Q&I time is not outrageously high, but will definitely have some form of performance hit.
Furthermore being 160+ TB of "Total Data Size on Disk" can you please confirm the hardware that is used to configure the DDB ?
As Pending delete is the primary concern you can also consider the following:
Recommendation - as of SP14 Commvault has also introduce enhancement to DDB (known as V5 DDB), which support what is known as (DDB) Pruning (Garbage Collection) - https://documentation.commvault.com/commvault/v11/article?p=108822.htm
"The Garbage Collection feature optimizes the DDB performance by reducing the DDB disk IO during the data pruning process. With the Garbage Collection feature, the DDB disk is parsed once every 24 hours to mark the CommServe job records for pruning and the data aging process prunes these marked CommServe job records."
Hopefully this helps