WordPress Heartbeat API
A while ago, I explained to you WordPress Heartbeat API and showed there also immediately, how the same can be deactivated effectively and quickly. The WordPress Heartbeat API is like a heartbeat or pulse that beats constantly and repeatedly. In the case of WordPress the heartbeat is not vital, it only communicates with the server in the background to find out if everything is still the same. This happens constantly and everywhere, in the dashboard, in the posts and so on. So the Heartbeat API is constantly beating and that is, as probably everyone can imagine, a strain on the performance, which is why disabling the Heartbeat API also relieves the CPU of a server accordingly. However, the Heartbeat API is also responsible for the constant communication in the background and things like the automatic saving of articles are no longer possible with deactivated API.
Here comes the WordPress Plugin heartbeat control into the game. This is the middle way for all those who want to reduce the load on the server but do not want to do without functions such as automatic saving. So Heartbeat Control reduces the pulse, slows down the heartbeat, if you like. In plain language: Instead of sending constant requests, the plugin reduces them to a fixed time span. For example, the WordPress Hearbeat API will only become active every 20 or 60 seconds, depending on what you have selected in the heartbeat control settings. This is very easy and relieves your server from now on, because the heartbeat of WordPress is simply shut down a little bit. Just to the most necessary. A bit like a coma patient.
Limit Heartbeat API
Personally, I have had excellent experiences with a complete deactivation of the WordPress Heartbeat API. Also because the backend of WordPress often stays open all day long and so, with activated Heartbeat API, requests are permanently sent in the background, which strains the server and generally reduces performance. But not everyone wants to do without automatic backups and the requests in the background, which often offer comfort and avoid problems. If this is the case, you can easily regulate the Hearbeat API with Hearbeat Control and at least stop the constantly repeating requests and bring it down to a healthy level. The plugin is relatively simple and lightweight, so it's not a mammoth project and no real ballast. For all those who don't want to disable the WordPress Hearbeat API completely, but still want to reduce the number of requests, the extension is definitely the right choice. one glance worth.