We use cloud container pools and recently noticed our DB and DB backups getting larger while data stg space and # of files staying about the same. We soon discovered our # of extentupdates growing, and never shrinking as they should be. Ideally, they should get processed frequently and reduce down to 0. Ours are over 200 million and growing daily. These records start to process if we restart TSM, but it really hits the system hard and eventually just stops processing extents for some reason. I know CHUNKDELETIONDELAY can be changed to slow down building the list of eligible extents, but I don't think this will help to control the actual deletion process itself. Any thoughts on this? Is there a way to control the # of threads used to process these extent deletions?