[wp-trac] [WordPress Trac] #61960: Heartbeat API: consider changing the min allowed time

[WordPress Trac]

#61960: Heartbeat API: consider changing the min allowed time
----------------------------+-----------------------------
 Reporter:  annezazu        |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  performance     |
----------------------------+-----------------------------
 In conversations with folks about phase 3 of WordPress compiled in
 [[https://make.wordpress.org/core/2023/10/23/summary-and-insights-of-
 phase-3-related-conversations/ | Summary and Insights of Phase 3 related
 conversations]] , getting locked out of a post and dealing with pain
 points around residual locking continually came up. While waiting for more
 collaborative workflows to be built, improving the locking experience in
 the interim would be a big improvement to day to day workflows. I chatted
 with @jorbin who mentioned that the heartbeat can be sped up so it checks
 every 15 seconds as it was originally set here:

 https://core.trac.wordpress.org/changeset/24406

 Historically, it seems this was done over a decade ago due to performance
 concerns on shared hosts:
 https://core.trac.wordpress.org/ticket/23216#comment:57 Is there space to
 revisit this and move it back to the original 5 seconds? Rather than
 dealing with getting locked out "hundreds of times a day" as one recent
 interviewee said, we could offer a way to lower the lock out time and ease
 people's workflows today.

 If a trac ticket has been open for this previously, I apologize! I did
 look around first before opening this one and appreciate being pointed to
 the right place as this does come up a fair amount when chatting with
 folks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61960>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform