[wp-trac] [WordPress Trac] #40022: Too much data in wp_options entry where option_name = 'cron' drags down WP

[WordPress Trac]

#40022: Too much data in wp_options entry where option_name = 'cron' drags down WP
-------------------------+-----------------------------
 Reporter:  yannielsen   |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Cron API     |    Version:  4.7.2
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Recently I experienced an installation running on a Cloud Server with 10GB
 RAM, 4 CPU cores being dragged down because of a plugin 'malfunctioning'
 with cron events.

 The plugin created excessive amounts of extra entries in wp_options entry
 where option_name = 'cron' resulting in a 15,4MB entry in the table.

 It wasn't a "endless loop"-error that suddenly resulted in it. It had gone
 unnoticed for quite some time before it got to the point where the server
 timed out because the requests to the database simply became too slow.

 The plugin should ofcourse not be doing that, but it got me wondering if
 it was an idea to implement a mechanism to split up the 'cron' entry into
 multiples when passing a threshold?

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