[wp-trac] [WordPress Trac] #23216: Create "WP Heartbeat" API

[WordPress Trac]

#23216: Create "WP Heartbeat" API
----------------------------+------------------
 Reporter:  azaozz          |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  3.6
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  autosave-redo   |
----------------------------+------------------

Comment (by DavidAnderson):

 @PaulGregory,

 The 0.3 of CPU time was only measuring the CPU usage due to the PHP CGI
 process, not of any other processes. Or, if you're referring to the laptop
 running hotter (no swapping, recent model), then you're ignoring the fact
 that that's still a real-world effect. People will file bug reports: "Hey,
 my laptop fan goes every time I log into my WordPress development site
 dashboard. Why does it do that? It never used to on 3.5!". They'll want a
 reply that does more than reference imaginary posters. What I'm saying is
 not "Hey, stop that, bad idea!", but that a more thorough evaluation of
 the likely effects - *or lack thereof* - would be potentially valuable;
 and consideration of whether some things slated for the "heartbeat" (e.g.
 logout warning) would be better achieved a less resource-intensive way. To
 give another real-world example, I lived in Africa for 5 years. Telling a
 website developer on a 6-year-old laptop that "yes, heartbeat is bringing
 your laptop to a grinding halt, but that's life in 2013! Get a new
 laptop!" is all the same as telling him "don't use WordPress, it's not for
 you!".

 David

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