Okay. Again, some performance issue and how to find/solve it will depend on the version of SQL Server as well. I assume that you have minimum SQL Server 2012R2, but maybe you are lucky and have 2016/2017. TempBD is a very live database. It can be small (zero at the moment of restart server, and after full backup), and can be big if you made backup only once per week (or never) and you never restart the server. If you have space for TempDB, unless it will go to 95-96% everything should be okay [that utilisation is only temporary, till the moment of commit]. But smaller utilisation of space is better of course.
Some extra places to look at:
:- TempDB database at MSDocs | https://learn.microsoft.com/en-us/sql/relational-databases/databases/tempdb-database?view=ve-server-ver15#:~:text=%20Starting%20with%20SQL%20Server%202016%20%2813.x%29%2C%20tempdb,a%20new%20instance%20installation.%20You%20can...%20More%20
- in the link above strongly recommended if video by Pam - she is a Goddess of TempDB (I mean really know the engine)
- "Three important things about TempDB" by my friend Pinal Dave | https://logicalread.com/3-things-sql-server-tempdb-performance-pd01/
- good article "Best Practice for SQL Server TempDB" by few my colleagues | https://logicalread.com/sql-server-tempdb-best-practices-multiple-files-w01/
- old but good article "TempDB Multiple Datafiles" | https://www.sqlservercentral.com/blogs/tempdb-multiple-datafiles
Did you looked for MSDocs article by Pedro Lopes: "DBCC SQLPERF (Transact-SQL)" https://learn.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-sqlperf-transact-sql?view=sql-server-ver15. I do not have actually SharePoint farm under my hands to check it in a real environment. Sorry.