Confluence 6.11 high CPU from the "WMI Provider Host" Service

[Administrator]

Hello,

since i upgrade to 6.11, i have a high CPU utilization from the "WMI Provider Host" service.

Bevor the upgrade, our server had around 12% CPU utilization. And now 77%. It is definitly the Confuence service. When i stop it, the CPU goes down to <5%.

What i have alrady tried:

Restart the server
Reinstall Confluence
Rebuild the Ancestor Table

Thank you for your help

[Shannon S · Accepted solution]

Hello everyone! @Administrator @Stephen Makk @Rene Frej Nielsen

I found one other user in our support system that has reported this issue so far, so I've initiated a bug ticket below for investigation:

• CONFSERVER-56346

It would help if you all can comment on that thread with your exact server details (OS version, JAVA version, database version, etc.) as well as with all the steps you took so far to resolve the issue. Feel free to provide any details at all you'd like to share there to help troubleshoot the problem.

One more thing you can do is review the following articles to see if any of it can help get the CPU down for you:

• WMI Provider Host High CPU Usage on Windows 10 - SOLVED
• WMI Provider Host High CPU Usage and Laptop...
• What is the WMI Provider Host wmiprvse.exe and why is it using so much CPU?

Feel free to include the details of these investigations in your comments on the bug ticket.

Thank you again for all your help!

Regards,

Shannon

[Shannon S]

@Administrator @Stephen Makk@Rene Frej Nielsen Good news!

As you've likely seen on the bug ticket I raised, this was previously discovered in 6.11.0 and is already fixed in the upcoming 6.11.1 release.

Stay tuned for that and once it's out and you're able to upgrade, you can confirm with us if you're no longer having the issue.

Regards,

Shannon

[Julian]

when is the release of 6.11.1 planned?

[Shannon S]

Hi Julian,

6.11.1 has already been released. You can review the Release Notes from our site.

Regards,

Shannon

[External IS OPS]

The problem still exists for me. Just updated to 6.11.1..  WMI HOST is using ~30% of my cpu..

[Administrator]

Here too, the update to 6.11.1 changed nothing.

[nogo_muc · Accepted solution]

Just to confirm: We are having the very same, extremely annoying effect.

We had Jira/Confluence on WS2012R2/SQL2012 previously, meanwhile completely rebuilded it on WS2016/SQL2016 with the latest Atlassian versions (7.11.2 & 6.11.0) and the situation remains unchanged:

6 vCores permanently loaded with 25% CPU (mainly burned by WMI host process).

@[deleted]: Pls. provide a fix asap.

[External IS OPS]

The update to 6.11.2 fixes this.

[External IS OPS]

Which means you're not on the latest version.. 6.11 incorrectly reported this bug as fixed.. they acknowledged their mistake and have corrected it in 6.11.2.. i'd get the lastest version.  Also if upgrading is not an option you can fix the symptom (high cpu usage) by disabling Collaborative editing, which was the source to the high wmi usage.

[nogo_muc]

Hi,

we followed your precious hint and disabled  Collaborative editing as an immediate measure. The CPU load went down immediately! We'll consider to update to the latest fix as well, but will do that later some when.

Many thanks and kind regards,

N.

[Paul Easter]

Thanks for the tip!!! Been struggling with this since upgrading to 6.11 over a month ago and this fixed my problem.  Will upgrade to 6.12 during our next maintenance cycle

[External IS OPS]

Glad I could help! :)

[Shannon S]

Hi there,

We have a few resources that can help you with this:

• Performance Troubleshooting Tools - Best Practice
• Crashes and Performance Troubleshooting
• Troubleshooting Confluence performance issues with thread dumps
• And double-check the hardware requirements here: Server Hardware Requirements

Let us know if you have any trouble.

Regards,

Shannon

[TBFO]

Upgraded to 6.12.0, and we are still facing the same issue. What happen?

[External IS OPS]

I'm guessing they re-introduced the bug.... You can fix the symptom (high cpu usage) by disabling Collaborative editing, which was the source to the high wmi usage.

[Maksym Fedoryshyh]

@TBFO can you please provide more details about your operating system (version), Confluence configuration (Datacenter or Server) and Synchrony running mode (managed by Confluence or standalone Synchrony cluster)?

On a side note, disabling of collaborative editing is unnecessary if you use Confluence  6.11.2 or higher. You can:

• Increase WMI Service polling interval by overriding synchrony.watch.pid.interval sys property for Synchrony (milliseconds). I'd recommend to start with 30 seconds (30000 milliseconds)
• Completely disable WMI Service polling by setting synchrony.watch.pid.disabled  sys property for Synchrony to true (not recommended).

This documentation has more details about how to configure Synchrony system properties.

Hope it helps.

[TBFO]

The issue left after the upgrade from 6.12.0 to 6.12.1.

The server runs Debian 9.5 on a single server instance.

[Maksym Fedoryshyh]

@TBFO is Debian a host OS for Confluence, or do you run Confluence on some kind of Windows VM, which runs on Debian?

(sorry for confusion, but "WMI Provider Host" is Windows-related problem, so I was a bit confused with Debian OS here)

[TBFO]

In our case, Confluence does not run on Windows at all (Linux VM running on qemu).

[Julian]

We have the same problem. Using Windows 2012R2 with SQL Server 2016 SP2. Confluence is constant taking 80% CPU (if Confluence is stopped, CPU usage is 3%), most of it goes to WMI (25-40%) - all the time.

User are complaining here and it's makes our whole server slow. 

[Administrator]

Thank you.

Nice to know that i am not alone with the problem.
I will wait for the next update. I dont like to spend to much time to analyse it.

A little bit strange is that 1 week after the update, my CPU goes down from 77% to 50%. Not like befor the update but better then befor.

[External IS OPS]

The update to 6.11.2 fixes this.

[Stephen Makk]

I am also getting this persistently.   Is clearly related to Confluence 6.11.   Have upgraded Postgres to latest version too.    No improvement.

[External IS OPS]

The update to 6.11.2 fixes this..

[Rene Frej Nielsen]

Hi,

I see this as well. It's definately something to do with versoin 6.11.

Regards,

René