[wp-trac] [WordPress Trac] #26050: Continual Admin Page POST (HeartBeats?) Can Cause SQL Connection Issues

[WordPress Trac]

#26050: Continual Admin Page POST (HeartBeats?) Can Cause SQL Connection Issues
-------------------------------------+------------------------------
 Reporter:  optimized-marketing.com  |       Owner:
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Autosave                 |     Version:  3.7.1
 Severity:  normal                   |  Resolution:
 Keywords:                           |     Focuses:
-------------------------------------+------------------------------

Comment (by lisota):

 Replying to [comment:3 azaozz]:

 We run a fairly large news site on WordPress with heavy traffic and a
 staff of 5-10 editors who spend their entire workday in wp-admin,
 specifically in edit posts screens.

 The heartbeat API, specifically the wp-refresh-auto-lock, is a major CPU
 hog. I can easily max out our 8-core server by opening 15-20 edit post
 windows and having them all hitting the server with refresh post lock
 requests every 15 seconds. Logging out of those screens quickly reduces
 CPU to under 10%.

 In our case, it appears to have less to do with MySQL connections and more
 to do with pure CPU utilization.

 I've deregistered the heartbeat script, as above, with a little bit of
 success, but I need to disable the 15 sec requests on the edit post
 screen. Any thoughts on how to accomplish this? We are willing to
 sacrifice post locking to get our wp-admin performance back.

 I tried deregistering heartbeat everywhere, including post.php and post-
 new.php. However, that seems to affect another AJAX function, the ajax tag
 search no longer works.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/26050#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform