We recently had the CPU of one of our Production Servers spike to 60 - 80% for about 45 minutes. The only thing we could see for processes using a lot of CPU were XE DISPATCHER, LOG WRITER and CHECKPOINT
Does anyone know what would cause this?
We recently had the CPU of one of our Production Servers spike to 60 - 80% for about 45 minutes. The only thing we could see for processes using a lot of CPU were XE DISPATCHER, LOG WRITER and CHECKPOINT
Does anyone know what would cause this?
I have a feeling that we have too little information to answer.
You say that the CPU spiked 60-80%, but you did not actually say that it was SQL Server that was using that CPU?
You post some output from a tool, but it is nothing that I recognize.
If there was an application submitting a lot queries, but each in its own connection, that may not appear in that tool.
Yes, SQL Server was the culprit for the High CPU usage. This is a screen shot from SpotLight. Looking at the process running at the time the ones that are consistently showing up with a high rate of CPU ms/s were LOG WRITER, XE DISPATCHER and CHECKPOINT.
There still seems to be something missing from the load. That is not 60-80% there. However, the XE_DISPATCHER is about 14 % which is lot for what I guess this process is doing. What extented event sessions do you have running?
This are the extended events running
Name
Long-Running Queries
SpotlightMonitoring_XXXXXXXXX_3843_CUSTDB_p03_sqlserver
system_health
telemetry_xevents
Hi @MahaneyRob-7897,
The high CPU usage is used for SQL server? We can get the CPU usage information from task manager as below screenshot.

If SQL server using CPU highly, please read below blog to troubleshot this issue.
TroubleShoot SQL High CPU Utilization
If the response is helpful, please clic*k "Accept Answer"* and upvote it, as this could help other community members looking for similar queries.
It is completely normal and expected for SQL Server to use all resources available to it for short periods of time. As a default SQL Server is allowed to use 100% of CPU. This is not an indication of a problem.
Correct. But I think this thread revealed that a seemlingly innocent-looking X-event session may affect the system load. I say "may", because we don't actually know if the workload suffered in the sense that it was not able to completed in the required time.
14 people are following this question.