[wp-trac] [WordPress Trac] #25073: Heartbeat performance and API improvements

[WordPress Trac]

#25073: Heartbeat performance and API improvements
-------------------------+------------------------------
 Reporter:  evansolomon  |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |
-------------------------+------------------------------
Changes (by azaozz):

 * cc: kadamwhite@… (removed)


Comment:

 Other TO-DOs for heartbeat:

 1. Ensure a "minimum connection rate" or completely remove the "skipping".
 This will depend on feedback from the hosting companies. Some
 alternatives:
  - Remove the "skipping" if there is no increased resource usage in 3.6 or
 if it's insignificant. As users spend most time on the Edit Post screen
 and heartbeat doesn't skip there (because of the post lock checks), any
 negative impact to shared hosting accounts should be measurable.
  - If the impact is more significant, only skip every other "beat" or
 ensure that heartbeat connects at least once every 45 (or 60) sec. when
 the user is active/window has focus.
 2. Consider completely stopping heartbeat if the user is inactive for 15
 (or 10) min. This will effectively release post locks. If the user becomes
 active later, heartbeat runs straight away so any notifications (lock
 taken over, login expired, etc.) will be shown almost immediately.
 3. Increase the "blurred" interval to 150 sec. so when a user has several
 tabs/windows open, heartbeat doesn't connect excessively. This will
 require changing the post locks expiration from 2 to 3 min.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/25073#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software