Deadlock query using extended events uses a lot of CPU resources on SQL Server host (4228897)

The extended events deadlock query can be a high consuming query on the SQL Server host that runs frequency and is listed in the top consuming list. Each execution is 11-25 seconds in duration and consumes CPU.

CPU increases on remote SQL Server host when the deadlock collection uses extended events.

RESOLUTION 1

Change "Deadlock working mode" to Trace to use the old SQL Server trace method to collect deadlock details.

RESOLUTION 2

Move the old system_health*.xel  files from SQL Server Log folder (e.g. "C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log") to another folder.