[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:6 azaozz]:

 This is very helpful. I was struggling to increase the heartbeat interval.
 There is a fair amount of incorrect guidance on the web about this
 setting.

 We are willing to sacrifice post locking by eliminating the wp-refresh-
 post-lock altogether. The CPU performance hit in our high traffic, multi-
 editor environment is huge and this has been affecting site performance
 for awhile now. It took us awhile to narrow down the exact cause, but it
 is definitely the large number of post lock refreshes via admin-ajax.

 I tried to deregister heartbeat.js on all pages, but as you noted, found
 other problems with post.js dependencies. (Namely that the tag box
 autocomplete doesn't function.)

 Can you provide any guidance on eliminating the wp-refresh-post-lock? I am
 thinking something like disabling the heartbeat event handlers like this:


 {{{
 jQuery(window).load( function() {
   jQuery(document).off('.refresh-lock');
   }
 });
 }}}

 I have managed to allow suspension of the heartbeat when post edit windows
 are left open for a long time via the following. Looks like this was added
 in 3.8.


 {{{
 remove_filter( 'heartbeat_settings', 'wp_heartbeat_set_suspension' );
 }}}

 I hope that as the Heartbeat API makes it into more features (i.e.
 autosave), that there can be some testing on high-traffic sites that
 intensively use the post editor. I'm sure none of this is even noticeable
 on smaller, infrequently-edited blogs. But on high traffic sites, it's
 been a CPU crusher.

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